[PHP] Re: Strange session problems. Please help.

2001-08-14 Thread lallous

I wish someone deletes this post!
It's posted with date 2002! I'm gonna see it on the top of my messages for
about a year now!
I'm using the news server and not mailing list!

"By Proxy" <[EMAIL PROTECTED]> wrote in message
005301c23ee3$27ba1500$[EMAIL PROTECTED]">news:005301c23ee3$27ba1500$[EMAIL PROTECTED]...
> Hi.
>
> Does anybody know of any issues in PHP 4.0B2 regarding to the handling of
> session variables on different networks?
>
> Here is the problem. I have written a user authentication system using
> session variables. When the user logs in their name and pass are stored as
> an associative array (with other details from a database). If the details
> are invalid the user is booted back to the logon screen. The system worked
> fine for everyone except myself and one other person who was on the same
> network (optus@home network).
>
> The problem was that although the username and password were sent and
stored
> into the session variables, upon accessing another page the session
> variables were not carried forward (although the session id was) and so I
> was thrown back to the login. As I said, this was only true for users on
the
> optus@home network. Fpr anyone else it seemed to be fine.
>
> Identical code on a server running PGP 4.0.4pl1 worked universally.
> I have been tearing my remaining hair out for days on this one now. Does
> anyone have any suggestions (except for 'Upgrade PHP on the 4.0B2 server'
or
> 'move to a different server'. That, unfortunately is beyond my control
:(  )
>
> Cheers
>
> Lee
>



-- 
PHP General 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] Re: Strange session problems. Please help.

2001-08-09 Thread Richard Lynch

Are there any firewalls involved?

If so, it's possible that some sort of authentication algorithm for packet
routing is breaking at some point that's not directly related to the
sessions, but to the header-forwarding -- Or even a badly-broken HTTP cache
on the firewalls.

Of course, if it's a badly-broken cache on Optus, you're screwed.

--
WARNING [EMAIL PROTECTED] address is an endangered species -- Use
[EMAIL PROTECTED]
Wanna help me out?  Like Music?  Buy a CD: http://l-i-e.com/artists.htm
Volunteer a little time: http://chatmusic.com/volunteer.htm
- Original Message -
From: By Proxy <[EMAIL PROTECTED]>
Newsgroups: php.general
To: php general list <[EMAIL PROTECTED]>
Sent: Thursday, August 08, 2002 8:54 AM
Subject: Strange session problems. Please help.


> Hi.
>
> Does anybody know of any issues in PHP 4.0B2 regarding to the handling of
> session variables on different networks?
>
> Here is the problem. I have written a user authentication system using
> session variables. When the user logs in their name and pass are stored as
> an associative array (with other details from a database). If the details
> are invalid the user is booted back to the logon screen. The system worked
> fine for everyone except myself and one other person who was on the same
> network (optus@home network).
>
> The problem was that although the username and password were sent and
stored
> into the session variables, upon accessing another page the session
> variables were not carried forward (although the session id was) and so I
> was thrown back to the login. As I said, this was only true for users on
the
> optus@home network. Fpr anyone else it seemed to be fine.
>
> Identical code on a server running PGP 4.0.4pl1 worked universally.
> I have been tearing my remaining hair out for days on this one now. Does
> anyone have any suggestions (except for 'Upgrade PHP on the 4.0B2 server'
or
> 'move to a different server'. That, unfortunately is beyond my control
  )
>
> Cheers
>
> Lee
>


-- 
PHP General 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]