Well that must mean that they are using session_name() and session_id(). I
really don't know why they are using that (considering it'll add
unnecessary overhead of calling session_name(),session_id() twice). My
guess is that they don't have a clue about the SID constant that
automatically ge
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
* and then Ed Gorski declared
> 1. This is done for users that don't use cookies. Believe it or not but
> there are people out there that are afraid of cookies and automatically
> turn them off. Without appending the sessionid to the end of
1. This is done for users that don't use cookies. Believe it or not but
there are people out there that are afraid of cookies and automatically
turn them off. Without appending the sessionid to the end of the URL,
sessions won't work for these people. Now how does your host append to the
e
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi all
I have 2 questions relating to how session id's are passed from page to
page:
1: My host uses the 'append to url and hidden fields' method. I dislike
this as it makes my urls untidy and my pages won't validate. So, is it
considered normal prac
4 matches
Mail list logo