Good morning Drew.
> > On the downside, i +still+ cant get the cookies to work,
> > although after faking a session via telnet it seems to work
> > jst fine. Set-Cookie and everything. It +seems+ to be setting
> > the cookie, but Apache is claiming that the browser doesnt
> > like them (and yes, i have double checked that cookies are
> > enabled on our netscape clients ;). I think its probably something
> > to do with the layout of the servers dirctories. FeH!
>
> One last thing: have you checked the path being sent with the cookie? I
> always use '/', so the browser always sends it back. Domain & Path are
> the two critical factors in cookies. Could you post the result HTTP
> headers for perusal?
Surely. I always use the path of '/' and the domain is always '.bmo.com'.
This (as i have mentioned) works fine from the cgi's, and I can see it being
put into Netscapes cookie file, but when I do it from Apache it doesnt get
even as far as that. All custom errors that are put into the Apache log
tells
me that this user has 'no cookies'.
It +has+ to be something i am doing wrong with Apache, it isnt netscape
(even made sure of this by using a windows machine to connect upto Apache
and still no joy). If its my code, then great. If its a compile problem then
thats more annoying, but my own fault. I can live with problems of my
own making ;)
Anyway, the ticket has the following (i jst duplicated the cgi headers
out call twice to get the header printed ;)
Date: Fri, 09 Jun 2000 15:38:52 GMT
Server: Apache/1.3.12 (Unix) mod_perl/1.24
Set-Cookie: Ticket=sessionID%3D1; domain=.bmo.com; path=/
Connection: close
Set-Cookie: Ticket=sessionID%3D1; domain=.bmo.com; path=/
Set-Cookie: Ticket=sessionID%3D1; domain=.bmo.com; path=/
Connection: close
Content-Type: text/html
the term to use here is 'what the f@#$' ?!
*re-reading my old code*
ARGH!
okay okay....i seem to be calling the Cookie once...i dont
+believe+ this. An old piece of code that I wrote in the cgi
many many moons ago is also doing a <meta tag> redirect
to a place which is 'locked down' so no one can get access
(it has a different reason for living ;).
So of course, I authenticate fine, it says okay, redirects me
to the originally requested page, which THEN redirects me
to another page where i CANT get access to. Becuase the
'/' directory is setup to always have the 403 return to the
login screen it happens +so+ fast i couldnt notice it.
DOH DOH DOH *beating head off of desk*
thanks drew and evryone else for putting up with my ramblings.
guess this means that I can take an 'early day' today then ;)
once again, many thanks and profoundest apologies ;)
^Stefss^
