Cookies from ASP.NET app not persisting even when enabled!
From: Lee Wilkie (lee_wilkie1_at_hotmail.com)
Date: 02/04/04
- Next message: Curt_C [MVP]: "Re: get redirect url before login"
- Previous message: Alvin Bruney [MVP]: "Re: DLLs in /bin do not load"
- Next in thread: bruce barker: "Re: Cookies from ASP.NET app not persisting even when enabled!"
- Reply: bruce barker: "Re: Cookies from ASP.NET app not persisting even when enabled!"
- Messages sorted by: [ date ] [ thread ]
Date: Wed, 4 Feb 2004 21:58:59 -0000
Dear All,
I'm new to ASP.NET and have been developing a small app at work to test
Forms Authentication. When running on my development machine (using
http://localhost/TestApp/Login.aspx for example) everything works fine -
that is, a successful (authenticated) login grants access to other app pages
and the authorization cookie is saved as expected on the local machine.
Unfortunately everything turns ugly when trying to 'test' the app from
Now having spent a 'good few' hours trying to figure this out, it seems that
So in short I believe that authorization is failing because the app cannot
Here's some info about my setup that may help a diagnosis!:
Dev machine is XP Pro running ASP.NET 1.1 and IIS 5.1.
As far as I know all machines have latest service packs/patches. ANY help
Thanks in advance,
Lee Wilkie.
another machine on the LAN (now using http://
name>/TestApp/Login.aspx rather than 'localhost'). The user enters their
credentials as usual and hits 'login' (and this is where it gets
interesting...), the app correctly authenticates the given user details
(I've added suitable response.write's to show this) but FAILS to authorize
the user and promptly redirects them back to the login page.
for whatever reason, any browser OTHER THAN the one on the development
machine FAILS TO PERSIST the authorization cookie (or any other cookie
created by the app for that matter) even though cookies are clearly enabled
on these browsers! I've witnessed that cookies from 'external' web sites are
persisting okay and are subject to IE's cookie settings but those cookies
from my app are simply not working. I've even used an HTTP 'inspection tool'
to view the app's server responses and can clearly see the 'Set-Cookie'
sections in the header!
'identify' the client due to the client failing to provide valid
authorization details given to it after a successful login.
IDE is VS.NET 2003.
Remote test machies are W2K, XP Pro and NT4 all with IE6.
would be much appreciated as this is driving me crazy.
Relevant Pages
... > if you site only works form a local browser, ... >> I'm new to ASP.NET and have been developing a small app at work to test ... >> and the authorization cookie is saved as expected on the local machine. ...
(microsoft.public.dotnet.framework.aspnet)
... > I'm new to ASP.NET and have been developing a small app at work to test ... > and the authorization cookie is saved as expected on the local machine. ... any browser OTHER THAN the one on the development ...
(microsoft.public.dotnet.framework.aspnet)
... I have two ASP.NET applications which I am trying to have share forms ... App B runs in a virtual sub-directory of App A. Both applications run ... to share the same authentication cookie. ... ..CommmunityServer cookie has been set. ...
(microsoft.public.dotnet.framework.aspnet)
... SinceADFSuses the same cookie ... and make sure the cookie paths for each app are /app1, /app2, /app3, etc. ... Joe Kaplan-MS MVP Directory Services Programming ... Co-author of "The .NET Developer's Guide to Directory Services Programming"http://www.directoryprogramming.net ...
(microsoft.public.windows.server.active_directory)
... Accessibility to ASP.NET app/pages is two step process: Authentication and ... ASP.NET app, whether the ASP.NET app is configured to use "Impersonation"... ... you can limit perticular users/groups' access to certain/all pages in ... Authorization may be necessary. ...
(microsoft.public.dotnet.framework.aspnet)