|
|
Posted by Steve on 10/17/06 14:02
"Mike" <mike@mjfcadsolutions.co.uk> wrote in message
news:1161071965.103729.34230@k70g2000cwa.googlegroups.com...
|
| >
| > Ok regarding sessions. Under default behaviour sessions will try and set
a
| > cookie, in the next page if the cookie does not exist it uses the
session id
| > in the address instead. If a cookie does exist it does not adapt the
| > address.
|
| But don't you need the php.ini file to have "session.use_trans_sid" to
| be 1? Its 0 in my ini file.
|
| >
| > Now regarding the problem of AOL. I do not think it is AOL not allowing
| > sessions, it sounds more like you use the IP number of the customer to
| > determin wether it is the same person. The problem with AOL is that a
user
| > can have 1 ip on 1 page load and on the next have another completely
| > different ip address.
|
| I don't use IP addresses to check if its the same person.
the session.use_trans_sid does not apply to ip addresses specifically.
enable it (set == 1) and make sure your version of php has that support
compiled in. the behavior peter mentioned is mostly true, however you have
full control of whether session data is set as cookie data or as data in a
file on your server. either way, php will rewrite your html output if you
are using sessions (you are beginning your script output with
session_start()...right?). look for the [Sessions] section of your php.ini
and note the options available and their respective descriptions. the
rewrite order by default is
"a=href,area=href,frame=src,input=src,form=fakeentry" this means that the
variable PHPSESSID will be added to this html so that when another page is
generated from these sources, the PHPSESSID will be sent as part of the
request...either as part of the query string or as part of your form data
(GET, POST).
you should have full control over your sessions regardless of the isp. you
may have to make some adjustments to your php.ini in order to get them to
behave as you'd like.
hth,
me
Navigation:
[Reply to this message]
|