Von: Luca Toscano [mailto:toscano.l...@gmail.com]
Gesendet: Samstag, 8. Juli 2017 09:52
An: Apache HTTP Server Development List
Betreff: Re: mod_proxy_fcgi and flush
Hi Jacob, Helmut!
2017-07-06 20:54 GMT+02:00 Jacob Champion
Based on the fact that Jim's advanced this for consideration for 2.4.28,
any further feedback on the following proposal to make RemoteIPProxyProtocol
directive into a whitelist (to compliment the current blacklist directive)? E.g.
in the spirit of the protocol, assign specific remote ip consumers
I am very confused, examined apr 1.6 threadproc deltas, now looking at the
mpm, but reporter isolated to apr. Next place I plan to look is is the
fileio abstraction.
I am beginning to suspect this is 'that customer'... In my experience, the
one who duct tapes and binds in entirely unrelated
Some time this week, I'm going to propose this patch for backport, since
I rely on it for the `make check` feature and I want to get that into 2.4.x.
Rainer, if you (or anyone else) have reservations, please let me know.
--Jacob
On 02/12/2016 09:46 AM, rj...@apache.org wrote:
Author: rjung
Hi Jean-Frederic,
On Mon, Jul 10, 2017 at 8:56 AM, jean-frederic clere wrote:
>
> According rfc1123 the configuration:
> ProxyPass "/" "balancer://127"
>
> BalancerMember ajp://tomcat1:8009
> BalancerMember ajp://tomcat2:8009
>
>
> 127 looks valid but it is rejected
Hi Rüdiger,
2017-07-10 8:31 GMT+02:00 Plüm, Rüdiger, Vodafone Group <
ruediger.pl...@vodafone.com>:
>
>
>
>
> *Von:* Luca Toscano [mailto:toscano.l...@gmail.com]
> *Gesendet:* Samstag, 8. Juli 2017 09:52
> *An:* Apache HTTP Server Development List
> *Betreff:* Re:
Hi,
According rfc1123 the configuration:
ProxyPass "/" "balancer://127"
BalancerMember ajp://tomcat1:8009
BalancerMember ajp://tomcat2:8009
127 looks valid but it is rejected by httpd, apr_parse_addr_port() takes
127 as port instead hostname.
So addr is NULL, then I have:
"AH01157:
Am 06.07.2017 um 19:28 schrieb Jacob Champion:
Administrators using prefork who would like to switch to HTTP/2 in the
future need to understand the limitations of the prefork architecture
they have selected. And sure, our users can request that we implement a
solution that "just works" with
Now that 2.4.27 is (almost) out, there are some other
patches in STATUS that would be good to finalize, including
in particular, the support for the HAproxy PROXY protocol
support. To help, I've gone ahead and created an updated,
merge-clean patch as well as created tests for it in the
Perl
> -Ursprüngliche Nachricht-
> Von: Jim Jagielski [mailto:j...@jagunet.com]
> Gesendet: Montag, 10. Juli 2017 15:33
> An: dev@httpd.apache.org
> Betreff: Re: rfc1123 aka Proxy balancer://127
>
> Personally, I think we simply document that balancer names
> must start w/ a character.
+1
On Thu, Jul 6, 2017 at 2:33 PM, William A Rowe Jr wrote:
> For your consideration... pre-release candidate tarballs of
> Apache legacy httpd 2.2.34 can be found in;
>
> http://httpd.apache.org/dev/dist/
>
> Thanks all who merged the security work in and other fixes,
> and
Personally, I think we simply document that balancer names
must start w/ a character.
> On Jul 10, 2017, at 2:56 AM, jean-frederic clere wrote:
>
> Hi,
>
> According rfc1123 the configuration:
> ProxyPass "/" "balancer://127"
>
>BalancerMember ajp://tomcat1:8009
>
Do I sense the sweet smell of monthly releases in the air?
> Am 10.07.2017 um 16:21 schrieb Jim Jagielski :
>
> Now that 2.4.27 is (almost) out, there are some other
> patches in STATUS that would be good to finalize, including
> in particular, the support for the HAproxy PROXY
On 06 Jul 2017, at 5:15 PM, Stefan Eissing wrote:
> This is not a bug, it is the collision of the processing models.
>
> So, I think disabling it prevent user from shooting themselves in the foot.
> If you are on prefork, you'd want the 6 parallel HTTP/1.1
14 matches
Mail list logo