Re: balancer-manager docs

Very nice! > Am 11.02.2016 um 18:46 schrieb Jim Jagielski : > > A rough and very brief framework of such a guide is now available... > >http://httpd.apache.org/docs/trunk/howto/reverse_proxy.html > > On 2016-02-10 06:21, Luca Toscano wrote: >>

Re: svn commit: r1729929 - in /httpd/httpd/trunk: CHANGES include/ap_mmn.h include/http_core.h include/httpd.h server/core.c

On Fri, Feb 12, 2016 at 2:04 AM, wrote: > Author: wrowe > Date: Fri Feb 12 01:04:58 2016 > New Revision: 1729929 > [] > Modified: httpd/httpd/trunk/include/httpd.h > URL: > http://svn.apache.org/viewvc/httpd/httpd/trunk/include/httpd.h?rev=1729929=1729928=1729929=diff >

Re: svn commit: r1729929 - in /httpd/httpd/trunk: CHANGES include/ap_mmn.h include/http_core.h include/httpd.h server/core.c

On Feb 12, 2016 2:24 AM, "Yann Ylavic" wrote: > > On Fri, Feb 12, 2016 at 2:04 AM, wrote: > > Author: wrowe > > Date: Fri Feb 12 01:04:58 2016 > > New Revision: 1729929 > > > > +/** Originator's DNS name, if known. NULL if DNS hasn't been checked, >

Re: balancer-manager docs

Looks very nice indeed! For being a "rough" version looks quite complete. Also the diagram is a cool addition to help people understand how reverse proxying works. I think the examples may need some adjusting with the matching slashes: ProxyPass "/" "http://www.example.com; should be: ProxyPass

Re: httpd-trunk/modules/http2 gets a proxy

Thanks. Added in r1729969. > Am 11.02.2016 um 21:52 schrieb NormW : > >

Re: svn commit: r1729927 - in /httpd/httpd/trunk/modules/ssl: ssl_engine_kernel.c ssl_private.h

On 02/12/2016 01:44 AM, rj...@apache.org wrote: > Author: rjung > Date: Fri Feb 12 00:44:22 2016 > New Revision: 1729927 > > URL: http://svn.apache.org/viewvc?rev=1729927=rev > Log: > Support for OpenSSL 1.1.0: > - further improvements for renegotiation > No more test suite failures for reneg,

Thoughts on using HW for httpd?

Hi folks, as some may know, ComDev is trialling a new thing called 'Help Wanted!' at https://helpwanted.apache.org/ I've added a few example entries for httpd, and I'm wondering if this is something we would want to plug into our web site? You can see an example web site widget at

Re: [users@httpd] Block access to "OPTIONS *"

Following up below users@ discussion on dev@... On Fri, Feb 12, 2016 at 12:47 PM, Yann Ylavic wrote: > On Fri, Feb 12, 2016 at 10:47 AM, Daniel wrote: >> The typical way to block OPTIONS in 2.2 does not need mod_rewrite at all >> IIRC. You just add

Re: [users@httpd] Block access to "OPTIONS *"

On Fri, Feb 12, 2016 at 1:28 PM, Jim Jagielski wrote: > Blocking OPTIONS has a long and illustrious history... > I am -0 on doing anything more related to it ;) OK, I see, let's users@ play with the workaround then :)

Re: Thoughts on using HW for httpd?

+1! I really like this idea, especially for new committers/volunteers like me looking for things to work on. I would also add a section related to "how to find help if you get stuck" or "How to send your code/work for review". Really interested, if you need any help I'll be available :) Luca

Re: svn commit: r1729929 - in /httpd/httpd/trunk: CHANGES include/ap_mmn.h include/http_core.h include/httpd.h server/core.c

On Fri, Feb 12, 2016 at 10:49 AM, William A Rowe Jr wrote: > On Feb 12, 2016 2:24 AM, "Yann Ylavic" wrote: >> >> I see this TODO about bitfield, but never seen it done in your >> commits, so I wonder where Rainer's warning comes from... >> Anyway, once

Re: Thoughts on using HW for httpd?

On 02/12/2016 02:06 PM, Luca Toscano wrote: > +1! > > I really like this idea, especially for new committers/volunteers like > me looking for things to work on. I would also add a section related to > "how to find help if you get stuck" or "How to send your code/work for > review". I think the

Re: [users@httpd] Block access to "OPTIONS *"

On 02/12/2016 01:28 PM, Jim Jagielski wrote: > Blocking OPTIONS has a long and illustrious history... > I am -0 on doing anything more related to it ;) > Isn't that why we have the optional mod_allowmethods these days anyway... With regards, Daniel.

Re: svn commit: r1729927 - in /httpd/httpd/trunk/modules/ssl: ssl_engine_kernel.c ssl_private.h

Yes, thanks for the review! Wrong checked version in "#if" (copy typo) fixed with r1729998. Regards, Rainer Am 12.02.2016 um 11:25 schrieb Ruediger Pluem: On 02/12/2016 01:44 AM, rj...@apache.org wrote: Author: rjung Date: Fri Feb 12 00:44:22 2016 New Revision: 1729927 URL:

Re: Thoughts on using HW for httpd?

/me like > On Feb 12, 2016, at 7:20 AM, Daniel Gruno wrote: > > Hi folks, > as some may know, ComDev is trialling a new thing called 'Help Wanted!' > at https://helpwanted.apache.org/ > > I've added a few example entries for httpd, and I'm wondering if this is > something

Re: [users@httpd] Block access to "OPTIONS *"

Blocking OPTIONS has a long and illustrious history... I am -0 on doing anything more related to it ;)

Re: [users@httpd] Block access to "OPTIONS *"

On Fri, Feb 12, 2016 at 1:29 PM, Daniel Gruno wrote: > On 02/12/2016 01:28 PM, Jim Jagielski wrote: >> Blocking OPTIONS has a long and illustrious history... >> I am -0 on doing anything more related to it ;) >> > > Isn't that why we have the optional mod_allowmethods these

Re: Thoughts on using HW for httpd?

+1! On Fri, Feb 12, 2016 at 1:27 PM, Jim Jagielski wrote: > /me like > >> On Feb 12, 2016, at 7:20 AM, Daniel Gruno wrote: >> >> Hi folks, >> as some may know, ComDev is trialling a new thing called 'Help Wanted!' >> at https://helpwanted.apache.org/ >>

Re: FYI: Backport of mod_proxy_hcheck

The patchfile, minus docs, can be found at: http://home.apache.org/~jim/patches/hcheck-2.4.patch Thx!

Re: FYI: Backport of mod_proxy_hcheck

I am following the way we've handled that struct before when we've needed to adjust (eg: uds_path)... > On Feb 12, 2016, at 9:14 AM, Yann Ylavic wrote: > > On Fri, Feb 12, 2016 at 2:50 PM, Jim Jagielski wrote: >> The patchfile, minus docs, can be found

Re: FYI: Backport of mod_proxy_hcheck

On Fri, Feb 12, 2016 at 2:50 PM, Jim Jagielski wrote: > The patchfile, minus docs, can be found at: > > http://home.apache.org/~jim/patches/hcheck-2.4.patch How about the changes to struct proxy_worker_shared w.r.t. backportability?

Re: mod_proxy_http2

I have renamed modules/http2/config.m4 to modules/http2/config2.m4 (note the "2" in front of the ".m4" suffix). AFAIK this will result in modules/http2 being handled after the module dirs which contain a normal config.m4. Thus the http2 modules get added after mod_proxy to the DSO_MODULES list

Re: httpd-trunk/modules/http2 gets a proxy

Am 12.02.2016 um 11:13 schrieb Stefan Eissing: Thanks. Added in r1729969. Am 11.02.2016 um 21:52 schrieb NormW : I got confused. Which file now builds mod_proxy_http2 on Netware? I can't find it. Shouldn't we also need a modules/http2/NWGNUmod_proxy_http2 file? Regards,

Re: httpd-2.4 --enable-load-all-modules side-effect

Am 08.02.2016 um 20:47 schrieb Rainer Jung: Hi Bill, Am 08.02.2016 um 19:11 schrieb William A Rowe Jr: ./configure [...] "--with-mods-shared=all" \ "--enable-mods-shared=all" \ "--enable-mpms-shared=all" \ "--enable-load-all-modules" \ "--with-mpm=worker" \ While this should be great for

rotatelogs and SIGTERM?

Recall that 2.2 ran piped loggers under a shell until somewhat late in life, and 2.4 runs them directly [by default]. rotatelogs currently doesn't do anything to block sigterm. The default ahndler for sigterm writes a short message to stderr, which is the only reason I noticed. It seems like a

Re: rotatelogs and SIGTERM?

IIRC, solaris is doing things like that. But here the shell would ignore SIGTERM (the trap may even be superfluous since shells usually ignore it implicitly), so it shouldn't be stopped by the signal and hence the message shouldn't show up... On Fri, Feb 12, 2016 at 10:40 PM, Eric Covener

Re: rotatelogs and SIGTERM?

On Fri, Feb 12, 2016 at 4:46 PM, Yann Ylavic wrote: > IIRC, solaris is doing things like that. > But here the shell would ignore SIGTERM (the trap may even be > superfluous since shells usually ignore it implicitly), so it > shouldn't be stopped by the signal and hence the

Re: rotatelogs and SIGTERM?

On Fri, Feb 12, 2016 at 8:25 PM, Eric Covener wrote: > Recall that 2.2 ran piped loggers under a shell until somewhat late in > life, and 2.4 runs them directly [by default]. > > rotatelogs currently doesn't do anything to block sigterm. The > default ahndler for sigterm

Re: rotatelogs and SIGTERM?

I lost a sentence somewhere. On one platform I use, the default for SIGTERM writes a message to stderr. On Fri, Feb 12, 2016 at 4:37 PM, Yann Ylavic wrote: > On Fri, Feb 12, 2016 at 8:25 PM, Eric Covener wrote: >> Recall that 2.2 ran piped loggers under

Re: httpd-trunk/modules/http2 gets a proxy

On 12/02/2016 9:13 PM, Stefan Eissing wrote: Thanks. Added in r1729969. Am 11.02.2016 um 21:52 schrieb NormW : Thanks, Norm

Re: httpd-trunk/modules/http2 gets a proxy

G/M And the start of yje weekend. On 13/02/2016 4:06 AM, Rainer Jung wrote: Am 12.02.2016 um 11:13 schrieb Stefan Eissing: Thanks. Added in r1729969. Am 11.02.2016 um 21:52 schrieb NormW : The .txt extension is a bogus extension added by my mailer I assume. I got

Re: svn commit: r1729929 - in /httpd/httpd/trunk: CHANGES include/ap_mmn.h include/http_core.h include/httpd.h server/core.c

On Feb 12, 2016 04:45, "Yann Ylavic" wrote: > > On Fri, Feb 12, 2016 at 10:49 AM, William A Rowe Jr wrote: > > On Feb 12, 2016 2:24 AM, "Yann Ylavic" wrote: > >> > >> I see this TODO about bitfield, but never seen it done in your