Mailing-List: contact users-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@httpd.apache.org
Received-SPF: pass (athena.apache.org: domain of tevans.uk@googlemail.com
 designates 74.125.83.45 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=googlemail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type;
        b=jo4O2M3kwA2DoGLGojbrXdSBS03re9b98qQaI3u3PLEGIiDfiNXxyzuKiBjp1a6K8p
         Y9X7+pzEVkmmpXUEEWTOhw9bs7Y34Z5Fl6uQ/B3KEqkHpwYYoMEuxiEU5XYXUYi6oD0k
         yaoLz5llP+xCQPB37QUJHgdf8w7x9idHWDVp0=
MIME-Version: 1.0
In-Reply-To: <AANLkTimLwMvUT2svqM6aJNqdVz4NqoxHopOa2Se_5nPj@mail.gmail.com>
References: <AANLkTik33IiRoebcWpy4I5uqFmTxKSP29u4WZ1esGEfM@mail.gmail.com>
	<AANLkTimJL_cmPFjOM7NZFKm1lNXlLq27ygqsx-rRvPMd@mail.gmail.com>
	<AANLkTikHcePyUvFYTamLKVcdqJXXoq8hlYTPRR-RCnEw@mail.gmail.com>
	<AANLkTinMnXGPFkRIqbT1UFe91UlSYBM3OCAf8SLtBQ91@mail.gmail.com>
	<AANLkTilZN7J5Jx66woLVHhagvAuI42YqHuQVGfJIvQA5@mail.gmail.com>
	<AANLkTimd9p4pBrePCLbjUJCMo9B1V3Jfp30vXYGFgSPf@mail.gmail.com>
	<AANLkTil_h-TeD7nE3iJw3QnwIgF4qeVZdzIq0iVATy4g@mail.gmail.com>
	<AANLkTikJtJoXDs37lVGdWw2wdQvae_Apz3oXI-L8BDAJ@mail.gmail.com>
	<AANLkTilLt8RICg15K5lQzs57diuROe7QxtRTGKSqFYkM@mail.gmail.com>
	<AANLkTiliCRgTYf3XcKU7Kw6MnqewnLidiz6c-3nt75fV@mail.gmail.com>
	<AANLkTilf8mITz1uUvsjDiABZXyLWGcBuWBWBbCc3bGj0@mail.gmail.com>
	<AANLkTinX7jtwxwRqYFKiU3bdIhNZbEtuCMll0Wi6AHBR@mail.gmail.com>
	<AANLkTimLwMvUT2svqM6aJNqdVz4NqoxHopOa2Se_5nPj@mail.gmail.com>
Date: Fri, 11 Jun 2010 16:31:16 +0100
Message-ID: <AANLkTimZvkDrXdRf_bG_3DgnZblejETtjPQrDUQ-zuNL@mail.gmail.com>
From: Tom Evans <tevans.uk@googlemail.com>
To: users@httpd.apache.org
Content-Type: text/plain; charset=UTF-8
Subject: Re: [users@httpd] rewrite rule for mingle

OK, that makes everything clearer.

BTW, you are proxying /mingle/. That final / has meaning, please be
precise about whether something has a trailing slash or not. Your
first examples of attempting to access '/mingle/' through the proxy
were requesting the URL '/mingle', which is why you got 404s. You did
later show logs where you had requested it properly, so I could
understand, but you must use the correct URLs, or things _wont_ work.

OK, so when you go to the proxy and request a mingle URL, the mingle
server returns this Location header:
Location: http://site.mydomain.com/profile/login

When you go directly, by specifying the IP address, the mingle server
returns this Location header:
Location: http://localhost:8080/profile/login

When this is processed by the proxy, it must be rewritten to this:
Location: http://site.mydomain.com/mingle/profile/login

so change this line in the configuration:
ProxyPassReverse /mingle/ http://192.168.1.10:8080/

to this:
ProxyPassReverse /mingle/ http://site.mydomain.com/

ProxyPassReverse roughly means this:
For each appropriate header, search for the second argument in the
value, and if found, replace with the first argument and reconstruct
the protocol, host and port according to the host headers/vhost name.

Restart apache, and re-do the tests.

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@httpd.apache.org
   "   from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org