Forms authentication problems

[Guest]

1. For some reason after the session has ended and the authentication cookie has expired I'm not being redirected to the login page. Insted I'm be assigned a new authentication cookie? Anyone have any ideas as to what may be causing this? (I'm using Microsoft's example

2. I'm also transferring a forms authentication cookie recieved from a web service (SQL Reporting Services) thru my app to the client. For some reason the expired cookie is sent in the request header and causes my app to break. Shouldn't the authentication cookie have expires set when retrieved from the Web Service and not just the expiration set on the authentication ticket inside the cookie? Right now when I translate from netcookie to httpcookie the expires is set to 1/1/1

Thanks

Mike

 

[Guest]

I figured out at least part of the problem... We are using Visual Source Safe in an isolated development model. We need to access sites @ xxx.domain.com so we setup the home directory of the default website in XP to point to our app. We then setup the Hosts file with xxx.domain.com as 127.0.0.1. This was causing the problem with not being redirected to the login page. If I access the app from http://localhost/xxx the cookies behave properly. If I access the app from either xxx.domain.com or http://localhost the cookies will not behave. This is one of the nightmarish problems I've had with cookies... I haven't checked if the reportserver cookie behaves properly yet. With my luck it won't. Is this why they named cookies "cookies" so you can hate them?

Mik

----- Mike wrote: ----

1. For some reason after the session has ended and the authentication cookie has expired I'm not being redirected to the login page. Insted I'm be assigned a new authentication cookie? Anyone have any ideas as to what may be causing this? (I'm using Microsoft's example

2. I'm also transferring a forms authentication cookie recieved from a web service (SQL Reporting Services) thru my app to the client. For some reason the expired cookie is sent in the request header and causes my app to break. Shouldn't the authentication cookie have expires set when retrieved from the Web Service and not just the expiration set on the authentication ticket inside the cookie? Right now when I translate from netcookie to httpcookie the expires is set to 1/1/1

Thanks

Mike

 

[John Saunders]

I figured out at least part of the problem... We are using Visual Source

Safe in an isolated development model. We need to access sites @
xxx.domain.com so we setup the home directory of the default website in XP
to point to our app. We then setup the Hosts file with xxx.domain.com as
127.0.0.1. This was causing the problem with not being redirected to the
login page. If I access the app from http://localhost/xxx the cookies behave
properly. If I access the app from either xxx.domain.com or http://localhost
the cookies will not behave. This is one of the nightmarish problems I've
had with cookies... I haven't checked if the reportserver cookie behaves
properly yet. With my luck it won't. Is this why they named cookies
"cookies" so you can hate them??

Mike, what is the domain of the cookies? Cookies will only be sent on a
request to that domain.