On Wed, 2009-04-01 at 16:03 +0200, Krist van Besien wrote: > On Wed, Apr 1, 2009 at 2:02 PM, <pthyseba@xxxxxxxxxxxxxx> wrote: > > > However, the proxied application has "login" functionality and thus sets a > > cookie. > > > > While I have been working on the revrese proxy setup for the last couple > > of days, I believe I'm now stuck: the proxied app is generating cookies > > with domain "remote", which I want to replace with domain "proxy" so that > > the client's browser will send the crorect cookie after logging in (as > > opposed to being redirected to the login screen every time...). > > Have you looked at > http://httpd.apache.org/docs/2.2/mod/mod_proxy.html#proxypassreversecookiedomain > > Krist OP specified he wants to do this on 2.0, which doesn't have ProxyPassReverseCookieDomain. As I see it, there are two solutions: 1) Use 2.2. It is what 2.0 was supposed to be anyways.. 2) Get the backend server to generate the correct content for the correct hostname. If you configure the proxy with ProxyPreserveHost, and then configure the backend system to respond to that host name. Then, no rewriting is required and everything will just work. Cheers Tom --------------------------------------------------------------------- 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@xxxxxxxxxxxxxxxx " from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
|