I haven't worked with trans_sid much, so I'm not very familiar with the
specifics.

The problem is that the get variable PHPSESSID or whatever is passed as a
get while the action of a form is POST.

One workaround is to create a hidden input named PHPSESSID or SID and set
it's value to <? echo $SID ?>.

Good luck, and let me know how you fixed it!!!  ;-)
-Joe

""Roman Lichszteld"" <[EMAIL PROTECTED]> wrote in message
9c6261$7pq$[EMAIL PROTECTED]">news:9c6261$7pq$[EMAIL PROTECTED]...
> I use Apache server with PHP 4 installed on WinNT 4.0,
session.use_trans_sid
> is set to 1, I don't use cookies.
>
> I have three pages, each looks like this:
>
> // test1.php
>
> <?
>   require("../php/checkuser.php");
>
>   print("Logged user: " . @$LoggedUserName . "<BR><BR>\n");
>
>   print("<FORM action=\"../php/test2.php\" method=\"post\">\n");  //
second
> page has action="/php/test3.php" and so on...
>   print("<INPUT type=\"submit\" name=\"Modify\" value=\"Next >>\">\n");
>   print("</FORM>\n");
> ?>
>
> Script "checkuser.php" simply calls "session_start()" and then check if
> variable 'LoggedUserName' isn't empty - in such case user is redirected to
> login page.
>
> Firts of these pages (test1.php) is called from main menu after
successfull
> login.
> Everything works fine: on first and second page SID is properly propagated
> but on third page script 'checkuser.php' ALWAYS redirects me to login
again.
> Is it possible that session ID becomes invalid after third page (menu ->
> test1 -> test2 -> ... )?!
>
> Had anyone similar problem?
>
> Regards
>
> Roman Lichszteld
> [EMAIL PROTECTED]
> [EMAIL PROTECTED]
>
>
>
>
> --
> PHP Windows Mailing List (http://www.php.net/)
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> To contact the list administrators, e-mail: [EMAIL PROTECTED]
>



-- 
PHP Windows Mailing List (http://www.php.net/)
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
To contact the list administrators, e-mail: [EMAIL PROTECTED]

Reply via email to