httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From <sebastien.allam...@orange.com>
Subject RE: [Bug 54319] New: ProxyPass has no effect in <Location> if rewrite occurs
Date Thu, 17 Jan 2013 15:20:53 GMT
Hi Eric,

This is not efficient for mobile access to use lot of redirects.

Meanwhile, we have successfully tested that we have the good behavior by just moving the ProxyPass
outside the Location & keeping in the Location our others treatments.

Do you confirm that is the good way to do it and that won't change in the future ?

I've got a final question, for the use of ProxyPassReverseCookiePath, how can we match it
on different path if it's not anymore inside the Location ??
Actually they are used in our Location, so they are applied only when there is a match for
the current Location..

ProxyPassReverseCookiePath  /  /titi/
ProxyPassReverseCookiePath  /  /toto/

If they are put outside the Location, How to decide which one to use ?

Regards,

Sebastien

-----Message d'origine-----
De : Eric Covener [mailto:covener@gmail.com] 
Envoyé : mercredi 2 janvier 2013 14:29
À : dev@httpd.apache.org
Objet : Re: [Bug 54319] New: ProxyPass has no effect in <Location> if rewrite occurs

On Wed, Jan 2, 2013 at 7:51 AM,  <sebastien.allamand@orange.com> wrote:
> Hi,
>
> In fact our problem is not in mod_rewrite usage but in the fact that proxypass don't
work anymore if we use it in Location section.
>
> We have our own module that dynamically modify the incoming request that we will forward
to different backend depending on our own conditions.
>
> To do that we modify the uri and match it with expected location section.
>
> But this don't works anymore in 2.4..

Apache manages per-request configuration for modules based on the nested set of <VirtualHost>,
<Directory>, <Location>, <If> etc.  that match the incoming request.

If mod_rewrite or your own custom module just changes the URI in place after the configuration
has been determined, it doesn't change the per-request configuration.

mod_proxy in 2.2 doesn't properly use per-request configuration, and crawls through every
ProxyPass every time.

Your module could send an internal redirect if it wanted the per-request configuration to
reflect the new URL.

_________________________________________________________________________________________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees
et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par
erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant
susceptibles d'alteration,
France Telecom - Orange decline toute responsabilite si ce message a ete altere, deforme ou
falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may
be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message
and its attachments.
As emails may be altered, France Telecom - Orange is not liable for messages that have been
modified, changed or falsified.
Thank you.


Mime
View raw message