EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] De la part de [EMAIL
> PROTECTED]
> Envoyé : lundi 15 octobre 2007 15:06
> À : users@httpd.apache.org
> Objet : Re: [EMAIL PROTECTED] Problems with ProxyPassReverseCookieDomain
>
> Distinguishing between FQDN and Domain is barely relevant wh
d'origine-
De : [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] De la part de [EMAIL PROTECTED]
Envoyé : lundi 15 octobre 2007 15:06
À : users@httpd.apache.org
Objet : Re: [EMAIL PROTECTED] Problems with ProxyPassReverseCookieDomain
Distinguishing between FQDN and Domain is barely relevant when discu
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 th
The behaviour observed by the original poster is correct: www.example.com is
the host FQDN - not the domain. The cookie _domain_ is example.com.
A cookie which domain is example.com will be submitted by the UA to both
www1.example.com and www.example.com. The conclusion is that no rewriting of
ProxyPassReverseCookieDomain does not change the cookie name - only the domain
field of the cookie.
Use LiveHTTPHeaders on Mozilla or similar (like Ethereal, burpproxy...) to see
exactly what the browser receives (Set-Cookie header) and what it subsequently
sends to the server in terms of cook
