Same POST data problem, different wording

[SteveCoppin]

Posting about this a couple of days ago but didn't get a complete answer..

I have written a Single Sign On (SSO) script that sits in my global.php The script takes credentials from the header and uses them to log the user in. The problem arises when the users session is interrupted and the have to be re-logged in. When this happens, they are logged in and do_login_redirect() is called. Somewhere down the line the post data ($_POST) isn't being carried through to the next page.

So, for example:

The user logs in and goes to post a reply. Takes longer than the timeout to write the reply and when they post the login process is kicked off. Behind the scenes the user is logged in and passed back to newreply.php, but the POST data is missing, leaving the user with no new post and just a friendly blank screen.

Does anyone have any idea how I can get around this.. A couple of ideas:

- Store the POST data somewhere where I can retrieve it again
- Not to redirect (but currently I am greeted with another blank screen when I comment out)

I have tried both of these but have had no luck. I'm very nearly out of ideas and patience and would really appreciate some help!!

If you don't understand the problem but would still like to help, please ask questions!

[Marco van Herwaarden]

Please continue in the original thread. If the response is not clear, ask for a better explanation.

Closing.