After updating 4.1.3 to 4.2.3 it is no longer possible to hold the connection via client.php. I found no entry at the help forum about that, so I think, nobody is using that interface?
It is possible run thru all actions, which can be performed without being connected.
Sending a connect I also can do that and the session ID was send to me.
With that ID I send a search and get the right results.
Sending a second search I will get the message "ERROR 12: use 'connect' action to initiate a session."
The problem is that a connect via client.php only set
$_SESSION=$user_id;
in session.php the code
if (!$SEARCH_SPIDER && !isset($_SESSION)) {
// A new session, so prevent session fixation attacks by choosing a new PHPSESSID.
session_regenerate_id(true);
$_SESSION=true;
}
generates a new session ID and delete the old one.
To solve that I can insert
$_SESSION=true;
after line 91 client.php
Is there an other idea to solve that problem?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
IIRC. GDBI stopped working with PGV 4.2. There is little reason for this great utility any more, but I think Daniel's still around, so maybe he can review your issue and respond. It did have a couple of terrific matching features.
Stephen
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
After updating 4.1.3 to 4.2.3 it is no longer possible to hold the connection via client.php. I found no entry at the help forum about that, so I think, nobody is using that interface?
It is possible run thru all actions, which can be performed without being connected.
Sending a connect I also can do that and the session ID was send to me.
With that ID I send a search and get the right results.
Sending a second search I will get the message "ERROR 12: use 'connect' action to initiate a session."
The problem is that a connect via client.php only set
$_SESSION=$user_id;
in session.php the code
if (!$SEARCH_SPIDER && !isset($_SESSION)) {
// A new session, so prevent session fixation attacks by choosing a new PHPSESSID.
session_regenerate_id(true);
$_SESSION=true;
}
generates a new session ID and delete the old one.
To solve that I can insert
$_SESSION=true;
after line 91 client.php
Is there an other idea to solve that problem?
IIRC. GDBI stopped working with PGV 4.2. There is little reason for this great utility any more, but I think Daniel's still around, so maybe he can review your issue and respond. It did have a couple of terrific matching features.
Stephen