httpd-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From solprovi...@apache.org
Subject [users@httpd] RE: Problems with ProxyPassReverseCookieDomain
Date Mon, 15 Oct 2007 08:11:10 GMT
An "example.com" Cookie will be sent to www.example.com and www1.example.com.

Questions for troubleshooting:
Is www.example.com receiving the Cookie?  (Should be yes.)
Is www.example.com sending the Cookie when proxying to
www1.example.com?  Is www1.example.com receiving the Cookie?  (Both
should be yes, but mod_proxy breaks in every other release.  This
2.2.1 changes state this issue was fixed.)
Does the server software on www1.example.com check the Domain field on
incoming Cookies and ignore Cookies from parent domains?  (Would mean
overengineering. If the Cookie arrives, use it.)

When you write "parameters", do you mean HTTP Headers, QueryString
parameters, POST parameters, part of the URL, or something else?

The parameters issue may require mod_rewrite.  Ttry this:
RewriteEngine On
RewriteRule ^/site/(.*)$ http://www1.example.com/$1 [P]

solprovider

===
From: Skiff Lad
On: 20071002 14:59
I seem to have a problem / misunderstanding regarding the use of the
ProxyPassReverseCookieDomain directive on 2.2.4 on Windows.

I have www.example.com running 2.2.4. Within the httpd.conf file, I
have a number of redirect directive statements that send a user, based
on the URL, eg. www.example.com/site1 to www1.example.com etc. This
all works fine so that the user arrives on the www1 box and there is a
cookie correctly set with name www1.example.com

It now transpires that I need to use ProxyPass to pass the parameters
coming in on the request to www.example.com onto www1.example.com - as
redirect doesn't send these initial parameters across.

So, my httpd.conf file (on www.example.com) now looks like:

ProxyPass /site1 http://www1.example.com
ProxyPassReverse /site1 http://www1.example.com
ProxyPassReverseCookieDomain www1.example.com www.example.com

But nothing seems to be happening. When I access
www.example.com/site1, there is a cookie correctly created (with the
right contents etc), however, it is named simply example.com, ie.
there is no www. nor www1. prefixing - this breaks subsequent
processing on the www1.example.com box because there is no cookie
named accordingly.

What am I doing wrong ? Do I need anything else ? Or am I being plain stupid ?

Thanks
Skiff

---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
   "   from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org


Mime
View raw message