httpd-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject Re: [users@httpd] Problems with ProxyPassReverseCookieDomain
Date Mon, 15 Oct 2007 17:40:42 GMT
I apologize for implying anything about your emotions. Maybe I am the
only one weeping over RFCs .  Bad specifications cause physical pain
to me. - solprovider

On 10/15/07, Axel-Stephane  SMORGRAV
<> wrote:
> Obviously the original poster has an application that only returns the domain part in
the cookie domain, hence the lack of rewriting despite ProxyPassReverseCookieDomain.
> and no I do not make a habit of weeping over RFCs.
> -ascs
> ____________________________________________
> -----Message d'origine-----
> De : [] De la part de
> Envoyé : lundi 15 octobre 2007 15:06
> À :
> Objet : Re: [users@httpd] Problems with ProxyPassReverseCookieDomain
> Distinguishing between FQDN and Domain is barely relevant when discussing Cookies.  RFC2965
states, "Domain Defaults to the request-host."  Cookies default to using the FQDN as the Domain
if the Domain is not specified.  Specified domains must start with a period, must be exactly
one level below the server name, and are only returned to servers in the one level above the
period.  Read Section 3.3.2 and weep.  The drafters deliberately made Cookies as limited as
> and cannot share Cookies even
> though both addresses reach the same server.   Look at the Cookies in
> your browser.  The server name will be part of the domain if no domain was specified
(e. g. and
> I wonder if the leading period is missing from "".
> "" (leading period) would be sent to and
 "" (no leading period) would only be sent to  Browsers should add
the leading period if domain is specified.
> solprovider

The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:> for more info.
To unsubscribe, e-mail:
   "   from the digest:
For additional commands, e-mail:

View raw message