Re: asp.net web farm configuration - (cookie domains?)

Tech-Archive recommends: Speed Up your PC by fixing your registry

From: Martin (x_at_y.z)
Date: 10/07/04 

Date: Thu, 7 Oct 2004 22:19:54 +0100

I guess if the machines in the web farm would have the same domain name (but
different IPs of course), then the cookie domain issue would go away, but I
had wanted the machine with the https pages to have a different name than
the other machines.

"Martin" <x@y.z> wrote in message
news:eq%234l4KrEHA.2776@TK2MSFTNGP14.phx.gbl...
> I'm plannig an asp.net web farm.
>
> I expect to use a SQL database for session state management, ie.
> <sessionState mode="SQLServer" cookieless="false" .../>
>
> My application uses web forms authentication, with a secure cookie, ie.
> <authentication mode="Forms">
> <forms name="mycookie" loginUrl=https://secure.domain.com
> requireSSL="true"/>
> </authentication>
>
> I expect different web applications on different web servers to be
> associated with each other by virtue of using the same sessionState
> settings.
>
> As indicated above, I would like to ensure that the pages requiring
> authentication are grouped together, and as it happens I am thinking that
> all the https pages would be grouped on one machine, and only these pages
> require authenticated access.
> So if I have 3 web servers, 1 and 2 would contain duplicate http pages
> allowing anonymous access, whilst 3 would contain https pages requiring
> authenticated access. All sharing the same session state, and being part
of
> the same overall web application.
>
> I would use <location> and <authorization> elements to achieve at the file
> level, or just <authorization> element in web.config placed in specific
sub
> directories.
>
>
> My question concerns cookies.
> Do the session and authentication cookies get shared between the different
> servers in the web farm? I would expect to be able to specify the cookie
> domain somewhere, but I can't see where.
>
> Thanks to anyone who can fill in the gaps of this plan.
> Martin
>
>

Relevant Pages

  • Re: asp.net web farm configuration - (cookie domains?)
    ... the session cookie is tied to domain/vdir. ... coding) session cookies from one application to another. ... > I guess if the machines in the web farm would have the same domain name ... >> My application uses web forms authentication, with a secure cookie, ie. ...
    (microsoft.public.dotnet.framework.aspnet)
  • asp.net web farm configuration - (cookie domains?)
    ... I'm plannig an asp.net web farm. ... I expect to use a SQL database for session state management, ... My application uses web forms authentication, with a secure cookie, ie. ...
    (microsoft.public.dotnet.framework.aspnet)
  • RE: Forms authentication cookie handling question (C#)
    ... I also replaced all of my ticket authentication code with the ... // Username and or password not found in our database... ... LoginControl's default code logic to generate authentication cookie. ...
    (microsoft.public.dotnet.framework.aspnet)
  • RE: Forms Authentication
    ... The DNS entry for my domain was not set corrretly, ... This should have overcome the cookie ... authentication ticketis not correctly set to the domain your ... Microsoft MSDN Online Support Lead ...
    (microsoft.public.dotnet.framework.aspnet)
  • RE: Forms authentication cookie handling question (C#)
    ... programmatically generate forms authentication ticket and set it in ASP.NET ... You use the Login control's "Authentication" event to do the user ... LoginControl's default code logic to generate authentication cookie. ...
    (microsoft.public.dotnet.framework.aspnet)