[prev in list] [next in list] [prev in thread] [next in thread]
List: apache-httpd-dev
Subject: Re: svn commit: r1773397 - in /httpd/httpd/trunk: CHANGES modules/proxy/mod_proxy.c
From: Luca Toscano <toscano.luca () gmail ! com>
Date: 2018-03-31 8:59:57
Message-ID: CAFedD40PZYyyE=5ghj9Mc46RJqwETbyMGDaw=urWnaf265s_Cg () mail ! gmail ! com
[Download RAW message or body]
2017-01-31 10:53 GMT+01:00 Plüm, Rüdiger, Vodafone Group <
ruediger.pluem@vodafone.com>:
>
>
> > -----Ursprüngliche Nachricht-----
> > Von: Joe Orton [mailto:jorton@redhat.com]
> > Gesendet: Dienstag, 31. Januar 2017 10:42
> > An: dev@httpd.apache.org
> > Betreff: Re: svn commit: r1773397 - in /httpd/httpd/trunk: CHANGES
> > modules/proxy/mod_proxy.c
> >
> > On Mon, Jan 30, 2017 at 07:52:03AM -0500, Eric Covener wrote:
> > > I have a fix but not sure if the change should just be reverted. In
> > > the PR, the user changed the 2.2 config to make the ProxyPass within
> > > location and expected similar behavior.
> > >
> > > Should have probably just told them that exceptions just could not be
> > > done that way.
> > >
> > > PR config is
> > >
> > > ProxyPass /error !
> > > <Location />
> > > ProxyPass http://foo/...
> > > </Location>
> > >
> > > It seemed useful at the time, but since stuffing the thing inside of
> > > Location is not all that more useful functionally, adding more code
> > > seems like a mistake.
> >
> > Asserting/documenting that higher-level exceptions don't apply for
> > ProxyPass within <Location> seems pretty reasonable to me.
> >
>
> +1
While reviewing https://bz.apache.org/bugzilla/show_bug.cgi?id=61225 I
tried to add some clarification with http://svn.apache.org/r1828069 (trunk
only for the moment, will wait a bit before backporting if anybody wants to
add/amend).
Luca
[Attachment #3 (text/html)]
<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">2017-01-31 \
10:53 GMT+01:00 Plüm, Rüdiger, Vodafone Group <span dir="ltr"><<a \
href="mailto:ruediger.pluem@vodafone.com" \
target="_blank">ruediger.pluem@vodafone.com</a>></span>:<br><blockquote \
class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid \
rgb(204,204,204);padding-left:1ex"><br> <br>
> -----Ursprüngliche Nachricht-----<br>
> Von: Joe Orton [mailto:<a \
href="mailto:jorton@redhat.com">jorton@redhat.com</a>]<br> > Gesendet: Dienstag, \
31. Januar 2017 10:42<br> > An: <a \
href="mailto:dev@httpd.apache.org">dev@httpd.apache.org</a><br> > Betreff: Re: svn \
commit: r1773397 - in /httpd/httpd/trunk: CHANGES<br> > \
modules/proxy/mod_proxy.c<br> <span class="gmail-">><br>
> On Mon, Jan 30, 2017 at 07:52:03AM -0500, Eric Covener wrote:<br>
> > I have a fix but not sure if the change should just be reverted. In<br>
> > the PR, the user changed the 2.2 config to make the ProxyPass within<br>
> > location and expected similar behavior.<br>
> ><br>
> > Should have probably just told them that exceptions just could not be<br>
> > done that way.<br>
> ><br>
> > PR config is<br>
> ><br>
> > ProxyPass /error !<br>
> > <Location /><br>
> > ProxyPass <a href="http://foo/." rel="noreferrer" \
target="_blank">http://foo/.</a>..<br> > > </Location><br>
> ><br>
> > It seemed useful at the time, but since stuffing the thing inside of<br>
> > Location is not all that more useful functionally, adding more code<br>
> > seems like a mistake.<br>
><br>
> Asserting/documenting that higher-level exceptions don't apply for<br>
> ProxyPass within <Location> seems pretty reasonable to me.<br>
><br>
<br>
</span>+1</blockquote><div><br></div><div>While reviewing <a \
href="https://bz.apache.org/bugzilla/show_bug.cgi?id=61225">https://bz.apache.org/bugzilla/show_bug.cgi?id=61225</a> \
I tried to add some clarification with <a \
href="http://svn.apache.org/r1828069">http://svn.apache.org/r1828069</a> (trunk only \
for the moment, will wait a bit before backporting if anybody wants to \
add/amend).</div><div><br></div><div>Luca </div></div><br></div></div>
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic