AW: svn commit: r1841225 - /httpd/httpd/trunk/modules/dav/main/props.c

C2 General > -Ursprüngliche Nachricht- > Von: Joe Orton > Gesendet: Dienstag, 25. Juni 2019 13:59 > An: dev@httpd.apache.org > Betreff: Re: svn commit: r1841225 - > /httpd/httpd/trunk/modules/dav/main/props.c > > On Tue, Jun 25, 2019 at 09:06:42AM +, Plüm,

AW: svn commit: r1841225 - /httpd/httpd/trunk/modules/dav/main/props.c

C2 General > -Ursprüngliche Nachricht- > Von: Joe Orton > Gesendet: Dienstag, 25. Juni 2019 10:45 > An: dev@httpd.apache.org > Betreff: Re: svn commit: r1841225 - > /httpd/httpd/trunk/modules/dav/main/props.c > > On Tue, Jun 25, 2019 at 08:49:08AM +0100, Joe Orton wrote: > > Unless I

AW: svn commit: r1841225 - /httpd/httpd/trunk/modules/dav/main/props.c

C2 General > -Ursprüngliche Nachricht- > Von: Joe Orton > Gesendet: Dienstag, 25. Juni 2019 09:49 > An: dev@httpd.apache.org > Betreff: Re: svn commit: r1841225 - > /httpd/httpd/trunk/modules/dav/main/props.c > > On Mon, Jun 24, 2019 at 09:54:21PM +0200, Ruediger Pluem wrote: > > On 0

Questions with mod_proxy_http2

I recently started using mod_proxy_http2 and some questions popped up for me: 1. Why do we retry 5 times hardcoded (leading to AH10023 in case we fail)? The other protocols only try to retry once if the ping failed (additional Expect 100 header in the HTTP case, PING packet in the AJP case). 2

AW: eor bucket

C2 General > -Ursprüngliche Nachricht- > Von: Yann Ylavic > Gesendet: Donnerstag, 9. Mai 2019 12:00 > An: httpd-dev > Betreff: Re: eor bucket > > On Thu, May 9, 2019 at 11:54 AM Yann Ylavic > wrote: > > > > On Thu, May 9, 2019 at 11:37 AM Stefan Eissing > > wrote: > > > > > > > Am

AW: eor bucket

C2 General > -Ursprüngliche Nachricht- > Von: Yann Ylavic > Gesendet: Donnerstag, 9. Mai 2019 11:54 > An: httpd-dev > Betreff: Re: eor bucket > > On Thu, May 9, 2019 at 11:37 AM Stefan Eissing > wrote: > > > > > Am 09.05.2019 um 11:32 schrieb Yann Ylavic : > > > > > > The issue is m

AW: eor bucket

I think your understanding is correct. Regards Rüdiger C2 General > -Ursprüngliche Nachricht- > Von: Stefan Eissing > Gesendet: Donnerstag, 9. Mai 2019 11:02 > An: dev@httpd.apache.org > Betreff: eor bucket > > Could someone help me to check my understanding of the eor bucket > imple

AW: svn commit: r1787606 - /httpd/httpd/trunk/server/core.c

C2 General > -Ursprüngliche Nachricht- > Von: Christophe JAILLET > Gesendet: Samstag, 4. Mai 2019 09:20 > An: dev@httpd.apache.org > Betreff: Re: svn commit: r1787606 - /httpd/httpd/trunk/server/core.c > > Hi, > > In my perpetual effort to synch 2.4 and trunk, I have stopped r1787606

AW: keep-alive and vary in 304 responses

C2 General > -Ursprüngliche Nachricht- > Von: Stefan Eissing > Gesendet: Mittwoch, 10. April 2019 14:40 > An: dev@httpd.apache.org > Betreff: Re: keep-alive and vary in 304 responses > > > > > Am 10.04.2019 um 14:07 schrieb Plüm, Rüdiger, Vodafone Gr

AW: keep-alive and vary in 304 responses

C2 General > -Ursprüngliche Nachricht- > Von: Yann Ylavic > Gesendet: Mittwoch, 10. April 2019 14:04 > An: httpd-dev > Betreff: Re: keep-alive and vary in 304 responses > > On Wed, Apr 10, 2019 at 1:03 PM Plüm, Rüdiger, Vodafone Group > wrote: > > >

AW: keep-alive and vary in 304 responses

C2 General > -Ursprüngliche Nachricht- > Von: Yann Ylavic > Gesendet: Mittwoch, 10. April 2019 12:49 > An: httpd-dev > Betreff: Re: keep-alive and vary in 304 responses > > On Wed, Apr 10, 2019 at 12:10 PM Stefan Eissing > wrote: > > > > > Am 09.04.2019 um 18:48 schrieb Roy T. Field

AW: keep-alive and vary in 304 responses

C2 General > -Ursprüngliche Nachricht- > Von: Stefan Eissing > Gesendet: Mittwoch, 10. April 2019 12:10 > An: dev@httpd.apache.org > Betreff: Re: keep-alive and vary in 304 responses > > > > Am 09.04.2019 um 18:48 schrieb Roy T. Fielding : > > > >> > >> 2. Validation responses lose

AW: [VOTE] Release httpd-2.4.39

up more readily on older OSs rather than newer ones. Plus, there's still a crap-ton of systems using CentOS5/RHEL5 On Mar 28, 2019, at 8:51 AM, Plüm, Rüdiger, Vodafone Group mailto:ruediger.pl...@vodafone.com>> wrote: C2 General -Ursprüngliche Nachricht- Von: Jim Jagiels

AW: AW: [VOTE] Release httpd-2.4.39

C2 General > -Ursprüngliche Nachricht- > Von: Dennis Clarke > Gesendet: Donnerstag, 28. März 2019 14:23 > An: dev@httpd.apache.org > Betreff: Re: AW: [VOTE] Release httpd-2.4.39 > > On 3/28/19 8:51 AM, Plüm, Rüdiger, Vodafone Group wrote: > > > > &

AW: [VOTE] Release httpd-2.4.39

C2 General > -Ursprüngliche Nachricht- > Von: Jim Jagielski > Gesendet: Donnerstag, 28. März 2019 13:39 > An: httpd > Betreff: Re: [VOTE] Release httpd-2.4.39 > > > > On Mar 27, 2019, at 11:09 AM, Daniel Ruggeri > wrote: > > > > Hi, all; > > Please find below the proposed releas

AW: svn commit: r1853953 - /httpd/httpd/trunk/modules/proxy/mod_proxy_http.c

My bad. I misread the diff. It was there in stream_reqbody_chunked and stream_reqbody_cl. So the condition is correct. Regards Rüdiger C2 General > -Ursprüngliche Nachricht- > Von: Yann Ylavic > Gesendet: Mittwoch, 20. Februar 2019 14:25 > An: httpd-dev > Betreff: Re: svn commit: r1

AW: svn commit: r1850745 - /httpd/httpd/trunk/modules/filters/config.m4

C2 General > -Ursprüngliche Nachricht- > Von: Stefan Eissing > Gesendet: Mittwoch, 16. Januar 2019 10:00 > An: dev@httpd.apache.org > Betreff: Re: svn commit: r1850745 - > /httpd/httpd/trunk/modules/filters/config.m4 > > > > > Am 16.01.2019 um 03:33 schrieb William A Rowe Jr clan.

AW: Plan to add sandbox branch

Just a quick and dirty idea and nothing beyond that worked out: How about to allow the balancer members to be configured via DNS SRV records? That should be very common in container environments. Regards Rüdiger Von: Christophe JAILLET Gesendet: Donnerstag, 29. November 2018 07:03 An: dev@htt

AW: ap_request_core_filter issues

> -Ursprüngliche Nachricht- > Von: Yann Ylavic > Gesendet: Dienstag, 23. Oktober 2018 13:09 > An: httpd-dev > Betreff: Re: ap_request_core_filter issues > > On Thu, Oct 18, 2018 at 1:52 PM Joe Orton wrote: > > > > On Thu, Oct 18, 2018 at 12:51:06PM +0200, Ruediger Pluem wrote: > > > >

AW: AW: [VOTE] Release httpd-2.4.36

t has been added recently in r1841508) :) I definitely need to document how to generate and use test-coverage data when running the test framework. This helps to spot where new tests are needed. CJ > Message du 11/10/18 10:08 > De : "Plüm, Rüdiger, Vodafone Group"

AW: [VOTE] Release httpd-2.4.36

Anyone else seeing t/modules/buffer.t(Wstat: 0 Tests: 12 Failed: 2) Failed tests: 8, 12 ? I don't see this with trunk on the same machine. Issue seems to be if input filtering is on on large POSTs. Regards Rüdiger > -Ursprüngliche Nachricht- > Von: Daniel Ruggeri

AW: svn commit: r1834924 - /httpd/httpd/branches/2.4.x/STATUS

> -Ursprüngliche Nachricht- > Von: Graham Leggett > Gesendet: Mittwoch, 10. Oktober 2018 19:12 > An: dev@httpd.apache.org > Betreff: Re: svn commit: r1834924 - /httpd/httpd/branches/2.4.x/STATUS > > On 28 Aug 2018, at 12:17, Ruediger Pluem wrote: > > >> On 07/20/2018 02:49 PM, Yann Yl

AW: svn commit: r1842540 - in /httpd/httpd/trunk: CHANGES modules/ssl/ssl_engine_kernel.c

> -Ursprüngliche Nachricht- > Von: Yann Ylavic > Gesendet: Montag, 8. Oktober 2018 23:46 > An: httpd-dev > Betreff: Re: svn commit: r1842540 - in /httpd/httpd/trunk: CHANGES > modules/ssl/ssl_engine_kernel.c > > On Fri, Oct 5, 2018 at 12:49 PM Ruediger Pluem > wrote: > > > > > > > > O

AW: svn commit: r1841225 - /httpd/httpd/trunk/modules/dav/main/props.c

t 09:30:25AM +, Plüm, Rüdiger, Vodafone Group > wrote: > > Thanks for reporting. Does the below patch cause the crash to go away? > > Yes, works for me!

AW: svn commit: r1841225 - /httpd/httpd/trunk/modules/dav/main/props.c

Thanks for reporting. Does the below patch cause the crash to go away? Index: main/mod_dav.c === --- main/mod_dav.c (revision 1841799) +++ main/mod_dav.c (working copy) @@ -2059,10 +2059,10 @@

AW: minor nit in mod_ssl

f: Re: minor nit in mod_ssl > >> > >> I am not opposed. However, there is an explanation added to the > request > >> error notes, which normally appears in the 403 response if I am not > >> mistaken? > >> > >> -Stefan > >> > >&g

AW: minor nit in mod_ssl

e if I am not > mistaken? > > -Stefan > > > Am 20.09.2018 um 11:40 schrieb Plüm, Rüdiger, Vodafone Group > : > > > > Can we have set it to info? Debug is very verbose for SSL just to find > out why a HTTP request was replied to with a 403. > > > > Regards

AW: minor nit in mod_ssl

Can we have set it to info? Debug is very verbose for SSL just to find out why a HTTP request was replied to with a 403. Regards Rüdiger Von: William A Rowe Jr Gesendet: Montag, 17. September 2018 22:27 An: httpd Betreff: Re: minor nit in mod_ssl On Mon, Sep 17, 2018 at 2:56 AM Stefan Eissin

AW: async mod_proxy_http

> -Ursprüngliche Nachricht- > Von: Yann Ylavic > Gesendet: Donnerstag, 13. September 2018 12:24 > An: httpd-dev > Betreff: Re: async mod_proxy_http > > On Thu, Sep 13, 2018 at 10:55 AM Plüm, Rüdiger, Vodafone Group > wrote: > > > > > -Urspr

AW: async mod_proxy_http

> -Ursprüngliche Nachricht- > Von: Yann Ylavic > Gesendet: Donnerstag, 13. September 2018 10:37 > An: httpd-dev > Betreff: Re: async mod_proxy_http > > On Thu, Sep 13, 2018 at 8:49 AM Plüm, Rüdiger, Vodafone Group > wrote: > > > > I don't li

AW: async mod_proxy_http

> -Ursprüngliche Nachricht- > Von: Eric Covener > Gesendet: Donnerstag, 13. September 2018 02:34 > An: Apache HTTP Server Development List > Betreff: Re: async mod_proxy_http > > On Wed, Sep 12, 2018 at 7:59 PM Yann Ylavic > wrote: > > > > On Wed, Sep 12, 2018 at 5:53 PM Eric Covener

AW: async mod_proxy_http

> -Ursprüngliche Nachricht- > Von: Yann Ylavic > Gesendet: Donnerstag, 13. September 2018 01:59 > An: httpd-dev > Betreff: Re: async mod_proxy_http > > On Wed, Sep 12, 2018 at 5:53 PM Eric Covener wrote: > > > > Forking from the Cool Stuff thread. > > > > Have you noticed that the wst

AW: 2.4.x and 2.6.x ... next steps

Von: William A Rowe Jr Gesendet: Mittwoch, 12. September 2018 03:15 An: httpd Betreff: Re: 2.4.x and 2.6.x ... next steps On Tue, Sep 11, 2018, 17:42 Graham Leggett mailto:minf...@sharp.fm>> wrote: On 11 Sep 2018, at 20:35, Jim Jagielski mailto:j...@jagunet.com>> wrote: We have never drop

AW: Buffer in apache

Von: Christophe JAILLET Gesendet: Dienstag, 21. August 2018 21:54 An: Hemant Chaudhary ; dev@httpd.apache.org; us...@httpd.apache.org Betreff: Re: Buffer in apache Le 21/08/2018 à 13:50, Hemant Chaudhary a écrit : Hi All, I want to use buffer of 512B in apache . I am using mod_proxy_http to s

AW: Win build success httpd-trunk

Von: Apache Lounge Gesendet: Donnerstag, 26. Juli 2018 13:32 An: dev@httpd.apache.org Betreff: Win build success httpd-trunk Build succeeded! Thanks Regards Rüdiger

AW: AW: Current trunk win build error

Can you try again with latest trunk including r1836613? This should make [2] obsolete. Regards Rüdiger > -Ursprüngliche Nachricht- > Von: Michal Karm > Gesendet: Mittwoch, 25. Juli 2018 10:28 > An: dev@httpd.apache.org; Plüm, Rüdiger, Vodafone Group > > Betreff: Re:

AW: Current trunk win build error

r1836603 @Windows folks: Can you please try if trunk mod_proxy builds again on Windows? Regards Rüdiger Von: William A Rowe Jr Gesendet: Dienstag, 24. Juli 2018 18:16 An: httpd Betreff: Re: Current trunk win build error +1, looks great.

AW: Current trunk win build error

oes work. Regards Rüdiger Von: William A Rowe Jr Gesendet: Montag, 23. Juli 2018 16:54 An: httpd Betreff: Re: Current trunk win build error I think it's simply the attached (couldn't apply the inline text patch). No need to change the hook name. On Mon, Jul 23, 2018 a

AW: Current trunk win build error

Replied in bugzilla. Question to our fellow Windows builders: Any issues to compile 2.4.34 currently in the way described in https://bz.apache.org/bugzilla/show_bug.cgi?id=62557#c5 Regards Rüdiger > -Ursprüngliche Nachricht- > Von: Michal Karm > Gesendet: Dienstag, 24. Juli 2018 07:54

AW: Current trunk win build error

: Re: Current trunk win build error I think it's simply the attached (couldn't apply the inline text patch). No need to change the hook name. On Mon, Jul 23, 2018 at 9:16 AM, Plüm, Rüdiger, Vodafone Group mailto:ruediger.pl...@vodafone.com>> wrote: So something like the below?

AW: Current trunk win build error

reff: Re: Current trunk win build error Perhaps use proxy_balancer_get_best_worker, and don't export that? That can be the delegate for ap_proxy_balancer_get_best_worker. We either keep callbacks local, or export them _NONSTD. All the *_DECLARE (without _NONSTD) are not usable as apr/httpd callbacks.

AW: Current trunk win build error

> -Ursprüngliche Nachricht- > Von: Apache Lounge > Gesendet: Montag, 23. Juli 2018 13:35 > An: dev@httpd.apache.org > Betreff: Current trunk win build error > > > > > > Error C2440 'initializing': cannot convert from 'proxy_worker > *(__stdcall *)(proxy_balancer *,request_rec > *,p

AW: mod_ssl and openssl 1.0.2 initialization

> -Ursprüngliche Nachricht- > Von: Yann Ylavic > Gesendet: Montag, 23. Juli 2018 11:50 > An: httpd-dev > Betreff: Re: mod_ssl and openssl 1.0.2 initialization > > On Wed, Jul 18, 2018 at 3:14 PM, Stefan Eissing > wrote: > > Something fishy reported in > > https://bz.apache.org/bugzill

AW: ocsp_force_default initialized with UNSET in httpd 2.4.34

Wrong revision. Correct one is r1836472. Regards Rüdiger > -Ursprüngliche Nachricht- > Von: Plüm, Rüdiger, Vodafone Group > Gesendet: Montag, 23. Juli 2018 11:26 > An: dev@httpd.apache.org > Betreff: AW: ocsp_force_default initialized with UNSET in httpd 2.4.34 &

AW: ocsp_force_default initialized with UNSET in httpd 2.4.34

This is now backported to 2.4.x as r1555631 and will be part of the next release. Regards Rüdiger > -Ursprüngliche Nachricht- > Von: Frank Meier > Gesendet: Freitag, 20. Juli 2018 09:26 > An: dev@httpd.apache.org > Betreff: Re: ocsp_force_default initialized with UNSET in httpd 2.4.34

AW: Bug in mod_ratelimit?

> -Ursprüngliche Nachricht- > Von: Yann Ylavic > Gesendet: Montag, 23. Juli 2018 10:52 > An: httpd-dev > Betreff: Re: Bug in mod_ratelimit? > > On Mon, Jul 23, 2018 at 7:45 AM, Plüm, Rüdiger, Vodafone Group > wrote: > > > > > >> ---

AW: svn commit: r1836381 - in /httpd/httpd/trunk: ./ include/ modules/proxy/ modules/proxy/balancers/

Von: William A Rowe Jr Gesendet: Freitag, 20. Juli 2018 23:03 An: httpd Betreff: Re: svn commit: r1836381 - in /httpd/httpd/trunk: ./ include/ modules/proxy/ modules/proxy/balancers/ On Fri, Jul 20, 2018, 15:22 Ruediger Pluem wrote: BTW: We have the same load ord

AW: Bug in mod_ratelimit?

> -Ursprüngliche Nachricht- > Von: Eric Covener > Gesendet: Sonntag, 22. Juli 2018 21:58 > An: Apache HTTP Server Development List > Betreff: Re: Bug in mod_ratelimit? > > > > You probably didn't test with chunked encoding (neither did I!), see > > > how ap_http_header_filter() adds th

AW: ocsp_force_default initialized with UNSET in httpd 2.4.34

I can do tomorrow and make a proposal in STATUS. Looks like we are all aligned now how to resolve this. Regards Rüdiger > -Ursprüngliche Nachricht- > Von: Stefan Eissing > Gesendet: Donnerstag, 19. Juli 2018 11:10 > An: dev@httpd.apache.org > Betreff: Re: ocsp_force_default initialized

AW: Time for 2.4.34?

> -Ursprüngliche Nachricht- > Von: Yann Ylavic > Gesendet: Donnerstag, 5. Juli 2018 21:34 > An: httpd-dev > Betreff: Re: Time for 2.4.34? > > On Thu, Jul 5, 2018 at 9:11 PM, Yann Ylavic > wrote: > > On Thu, Jul 5, 2018 at 5:43 PM, Jim Jagielski wrote: > >> Seems to me that we are jus

AW: svn commit: r1682074 - in /httpd/httpd/branches/2.4.x: ./ STATUS modules/ssl/ssl_engine_init.c

> -Ursprüngliche Nachricht- > Von: Christophe Jaillet > Gesendet: Samstag, 30. Juni 2018 14:08 > An: dev@httpd.apache.org > Betreff: Re: svn commit: r1682074 - in /httpd/httpd/branches/2.4.x: ./ > STATUS modules/ssl/ssl_engine_init.c > > Le 27/05/2015 à 18:33, wr...@apache.org a écrit :

AW: Host header checking too strict?

> -Ursprüngliche Nachricht- > Von: Eric Covener > Gesendet: Freitag, 22. Juni 2018 23:21 > An: Apache HTTP Server Development List > Betreff: Host header checking too strict? > > After CVE-2016-8743 we only accept hostnames that are valid in DNS, > which notably excludes underscores.

AW: Brigade memory lifetime & leaks

> -Ursprüngliche Nachricht- > Von: Joe Orton > Gesendet: Dienstag, 5. Juni 2018 14:48 > An: dev@httpd.apache.org; d...@apr.apache.org > Betreff: Re: Brigade memory lifetime & leaks > > On Tue, Jun 05, 2018 at 12:07:31PM +, Plüm, Rüdiger, Vodafone Gro

AW: Brigade memory lifetime & leaks

> -Ursprüngliche Nachricht- > Von: Stefan Eissing > Gesendet: Dienstag, 5. Juni 2018 13:27 > An: dev@httpd.apache.org > Cc: d...@apr.apache.org > Betreff: Re: Brigade memory lifetime & leaks > > > > > Am 05.06.2018 um 10:46 schrieb Joe Orton : > > > > In 2.4's http_request.c there ar

AW: A proposal...

> -Ursprüngliche Nachricht- > Von: Eric Covener > Gesendet: Dienstag, 24. April 2018 15:31 > An: Apache HTTP Server Development List > Betreff: Re: A proposal... > > On Tue, Apr 24, 2018 at 8:50 AM, Jim Jagielski wrote: > > One idea is that we setup, using the existing perl test frame

AW: A proposal...

> -Ursprüngliche Nachricht- > Von: Rainer Jung > Gesendet: Montag, 23. April 2018 16:47 > An: dev@httpd.apache.org > Betreff: Re: A proposal... > > Am 23.04.2018 um 16:00 schrieb Jim Jagielski: > > It seems that, IMO, if there was not so much concern about > "regressions" in releases, t

AW: A proposal...

> -Ursprüngliche Nachricht- > Von: Stefan Eissing > Gesendet: Montag, 23. April 2018 17:08 > An: dev@httpd.apache.org > Betreff: Re: A proposal... > > Such undocumented and untested behaviour, which nevertheless is > considered a regression, cannot be avoided, since it cannot be > antic

AW: Revisit Versioning? (Was: 2.4.3x regression w/SSL vhost configs)

> -Ursprüngliche Nachricht- > Von: David Zuelke > Gesendet: Montag, 23. April 2018 18:09 > An: dev@httpd.apache.org > Betreff: Re: Revisit Versioning? (Was: 2.4.3x regression w/SSL vhost > configs) > > On Sat, Apr 21, 2018 at 12:45 PM, Graham Leggett > wrote: > > On 19 Apr 2018, at 5:5

AW: So... when should we do 2.4.34? [WAS: Re: Revisit Versioning? (Was: 2.4.3x regression w/SSL vhost configs)]

I am also more in the "ship when it is ready", then "ship when it is time" boat. We probably could have some automated "nightlyies" which are not releases in the ASF sense (as release requires voting), but only some sort of convenience transformation of an svn export / co that creates a tar ball.

AW: "Most Popular Web Server?"

> -Ursprüngliche Nachricht- > Von: Daniel Ruggeri [mailto:drugg...@primary.net] > Gesendet: Donnerstag, 19. April 2018 02:22 > An: dev@httpd.apache.org > Betreff: Re: "Most Popular Web Server?" > > On 4/18/2018 11:46 AM, Jim Jagielski wrote: > > > Personally, I'd like to see the the PMC

AW: /scheme/i sensitivity? (was: svn commit: r1829430 - /httpd/httpd/patches/2.4.x/core-check_errorlog_dir_syslog.patch)

> -Ursprüngliche Nachricht- > Von: William A Rowe Jr [mailto:wr...@rowe-clan.net] > Gesendet: Mittwoch, 18. April 2018 18:49 > An: httpd > Betreff: /scheme/i sensitivity? (was: svn commit: r1829430 - > /httpd/httpd/patches/2.4.x/core-check_errorlog_dir_syslog.patch) > > On Wed, Apr 18,

AW: SNI normalization?

I guess this makes sense to avoid these kind of issues. Regards Rüdiger > -Ursprüngliche Nachricht- > Von: Stefan Eissing [mailto:stefan.eiss...@greenbytes.de] > Gesendet: Mittwoch, 11. April 2018 11:49 > An: dev@httpd.apache.org > Betreff: SNI normalization? > > Feedback desired: > >

AW: [POLL] Final status of 2.2.x branch

> -Ursprüngliche Nachricht- > Von: Rich Bowen [mailto:rbo...@rcbowen.com] > Gesendet: Mittwoch, 7. März 2018 21:11 > An: dev@httpd.apache.org > Betreff: Re: [POLL] Final status of 2.2.x branch > > > On 02/22/2018 01:27 PM, William A Rowe Jr wrote: > > On Thu, Feb 22, 2018 at 6:53 AM, Lu

AW: [POLL] Final status of 2.2.x branch

> -Ursprüngliche Nachricht- > Von: Eric Covener [mailto:cove...@gmail.com] > Gesendet: Mittwoch, 21. Februar 2018 16:51 > An: Apache HTTP Server Development List > Betreff: Re: [POLL] Final status of 2.2.x branch > > > In the absence of three active contributors, I volunteer to clean up

AW: svn commit: r1824592 - /httpd/httpd/branches/2.4.x/STATUS

> -Ursprüngliche Nachricht- > Von: Joe Orton [mailto:jor...@redhat.com] > Gesendet: Dienstag, 20. Februar 2018 09:20 > An: dev@httpd.apache.org > Betreff: Re: svn commit: r1824592 - /httpd/httpd/branches/2.4.x/STATUS > > On Mon, Feb 19, 2018 at 08:38:05PM +0100, Ruediger Pluem wrote: > >

AW: Binary Breakage (was: svn commit: r1824592 - /httpd/httpd/branches/2.4.x/STATUS)

> -Ursprüngliche Nachricht- > Von: William A Rowe Jr [mailto:wr...@rowe-clan.net] > Gesendet: Dienstag, 20. Februar 2018 22:29 > An: httpd > Betreff: Re: Binary Breakage (was: svn commit: r1824592 - > /httpd/httpd/branches/2.4.x/STATUS) > > On Tue, Feb 20, 2018 at 2:57 PM, Ruediger Plue

AW: New ServerUID directive

> -Ursprüngliche Nachricht- > Von: Jim Jagielski [mailto:j...@jagunet.com] > Gesendet: Freitag, 2. Februar 2018 15:15 > An: httpd > Betreff: Re: New ServerUID directive > > Why? If it is designed to not change between restarts then > there are much easier ways to be unique, which it kin

AW: svn commit: r1822878 - in /httpd/httpd/trunk/modules: http2/h2_config.c http2/h2_config.h http2/h2_conn.c http2/mod_http2.c http2/mod_http2.h proxy/config.m4 proxy/proxy_util.c

> -Ursprüngliche Nachricht- > Von: Stefan Eissing [mailto:stefan.eiss...@greenbytes.de] > Gesendet: Donnerstag, 1. Februar 2018 16:15 > An: dev@httpd.apache.org > Betreff: Re: svn commit: r1822878 - in /httpd/httpd/trunk/modules: > http2/h2_config.c http2/h2_config.h http2/h2_conn.c http2

AW: svn commit: r1822849 - /httpd/httpd/trunk/modules/proxy/proxy_util.c

> -Ursprüngliche Nachricht- > Von: Yann Ylavic [mailto:ylavic@gmail.com] > Gesendet: Donnerstag, 1. Februar 2018 09:49 > An: httpd-dev > Betreff: Re: svn commit: r1822849 - > /httpd/httpd/trunk/modules/proxy/proxy_util.c > > On Thu, Feb 1, 2018 at 9:36 AM,

AW: svn commit: r1822849 - /httpd/httpd/trunk/modules/proxy/proxy_util.c

Thanks for the review. Does r1822858 address your concern? Regards Rüdiger Von: Greg Stein [mailto:gst...@gmail.com] Gesendet: Donnerstag, 1. Februar 2018 09:01 An: dev@httpd.apache.org Betreff: Re: svn commit: r1822849 - /httpd/httpd/trunk/modules/proxy/proxy_util.c On Thu, Feb 1, 2018 at 1

AW: Pruning working branches (Was: Re: Why?)

+1 Regards Rüdiger > -Ursprüngliche Nachricht- > Von: Yann Ylavic [mailto:ylavic@gmail.com] > Gesendet: Donnerstag, 26. Oktober 2017 10:31 > An: httpd-dev > Betreff: Re: Pruning working branches (Was: Re: Why?) > > I like this "attic" idea better, resurrecting something is easier i

AW: [Proposal] 2.5.x -> 2.6.0/3.0.0 transition guidelines

> -Ursprüngliche Nachricht- > Von: William A Rowe Jr [mailto:wr...@rowe-clan.net] > Gesendet: Dienstag, 24. Oktober 2017 19:00 > An: httpd > Betreff: [Proposal] 2.5.x -> 2.6.0/3.0.0 transition guidelines > > I'd like to propose the following, so we can decide on what course to > chart b

AW: svn commit: r1813167 - in /httpd/httpd/trunk: CHANGES modules/proxy/mod_proxy.c modules/proxy/mod_proxy_balancer.c

Same here: I don't see why the lbmethods rely on it between 1 and 100 and why they cannot work with 100 till 1 Effectively we kill values like 2.5 and the new comment > it is a number between 1 and 100 (or 0.01 and 1.0). is wrong since 0.01 is not an allowed value (it will fail the check bel

AW: Pruning working branches (Was: Re: Why?)

> -Ursprüngliche Nachricht- > Von: William A Rowe Jr [mailto:wr...@rowe-clan.net] > Gesendet: Dienstag, 24. Oktober 2017 15:12 > An: httpd > Betreff: Pruning working branches (Was: Re: Why?) > > On Tue, Oct 24, 2017 at 3:28 AM, Steffen wrote: > > > > On Tuesday 24/10/2017 at 10:26, Ste

AW: Simplify download distribution directory by dropping sha1 hashes?

Sounds reasonable to me. Regards Rüdiger > -Ursprüngliche Nachricht- > Von: William A Rowe Jr [mailto:wr...@rowe-clan.net] > Gesendet: Montag, 23. Oktober 2017 20:37 > An: httpd > Betreff: Simplify download distribution directory by dropping sha1 > hashes? > > HTTPD team, > > Since ou

AW: mod_rewrite, vary headers and internal redirects

I would tend to say that the code is correct and the RewriteCond code is wrong, because it doesn’t matter if the condition becomes true or false. The headers value has an influence on the result. Tricky question is what to do regarding Vary if the non-presence of a header has an influence. Reg

AW: svn commit: r1812393 - in /httpd/httpd/branches/2.4.x: ./ STATUS modules/http2/ modules/http2/config2.m4

Good point. The original desire was to have lib64 as fallback in order to keep the default as is with lib. But probably the reverse order (64 over 32) makes more sense these days. Keen to hear what others say. Regards Rüdiger Von: William A Rowe Jr [mailto:wr...@rowe-clan.net] Gesendet: Dienst

AW: backport patches

+1 Regards Rüdiger > -Ursprüngliche Nachricht- > Von: Yann Ylavic [mailto:ylavic@gmail.com] > Gesendet: Donnerstag, 12. Oktober 2017 13:24 > An: httpd-dev > Betreff: Re: backport patches > > On Thu, Oct 12, 2017 at 1:18 PM, Plüm, Rüdiger, Voda

AW: backport patches

> -Ursprüngliche Nachricht- > Von: Yann Ylavic [mailto:ylavic@gmail.com] > Gesendet: Donnerstag, 12. Oktober 2017 13:12 > An: httpd-dev > Betreff: Re: backport patches > > > FYI: I just checked in a "patches" directory inside the 2.4.x branch. > > I hope it's not picked up in a sour

AW: svn commit: r1811192 - /httpd/httpd/trunk/.gdbinit

Does r1811570 fix your issue? Regards Rüdiger Von: Luca Toscano [mailto:toscano.l...@gmail.com] Gesendet: Montag, 9. Oktober 2017 15:34 An: Apache HTTP Server Development List Betreff: Re: svn commit: r1811192 - /httpd/httpd/trunk/.gdbinit Hi Ruediger, 2017-10-05 14:01 GMT+02:00 mailto:rpl...

AW: httpd memory consumption

Von: William A Rowe Jr [mailto:wr...@rowe-clan.net] Gesendet: Samstag, 7. Oktober 2017 15:52 An: httpd Betreff: Re: httpd memory consumption Have you tried bisecting the config directives to see which is triggering the memory abuse? Sounds like the module might not be async-ready, but should

.gdbinit changes backports. CTR or RTC?

Is backporting .gdbinit changes to a stable branch CTR or RTC? Regards Rüdiger

AW: C-L filter buffering snafu

Just put a reply in bugzilla (https://bz.apache.org/bugzilla/show_bug.cgi?id=61222#c4), plus a patch proposal. Reilly weird that we have not been hit by this for such a long time. I think we should not buffer. Regards Rüdiger > -Ursprüngliche Nachricht- > Von: Joe Orton [mailto:jor...@

AW: CVE-2017-9788: Uninitialized memory reflection in mod_auth_digest

http://svn.apache.org/r1800955 Regards Rüdiger Von: Rashmi Srinivasan [mailto:rashmisrinivasan2...@gmail.com] Gesendet: Montag, 17. Juli 2017 07:50 An: dev@httpd.apache.org Cc: us...@httpd.apache.org Betreff: Re: CVE-2017-9788: Uninitialized memory reflection in mod_auth_digest Hi, Please can

AW: mod_proxy_fcgi and flush

Von: Luca Toscano [mailto:toscano.l...@gmail.com] Gesendet: Freitag, 14. Juli 2017 11:30 An: Apache HTTP Server Development List Betreff: Re: mod_proxy_fcgi and flush Hi Yann, 2017-07-13 22:15 GMT+02:00 Yann Ylavic mailto:ylavic@gmail.com>>: On Thu, Jul 13, 2017 at 7:36 PM, Luca Toscano

AW: rfc1123 aka Proxy balancer://127

> -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 R

AW: mod_proxy_fcgi and flush

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 mailto:champio...@gmail.com>>: On 07/06/2017 11:13 AM, Jim Jagielsk

AW: svn commit: r1800181 - /httpd/httpd/branches/2.4.x/STATUS

FWIW: I am fine with Yann’s proposal as well. Regards Rüdiger Von: William A Rowe Jr [mailto:wr...@rowe-clan.net] Gesendet: Mittwoch, 28. Juni 2017 19:28 An: httpd Cc: c...@httpd.apache.org Betreff: Re: svn commit: r1800181 - /httpd/httpd/branches/2.4.x/STATUS Actually, I should have backed ou

AW: Timeouts and other time-related granularity

> -Ursprüngliche Nachricht- > Von: Stefan Eissing [mailto:stefan.eiss...@greenbytes.de] > Gesendet: Dienstag, 20. Juni 2017 15:13 > An: dev@httpd.apache.org > Betreff: Re: Timeouts and other time-related granularity > > > > Am 20.06.2017 um 14:56 schrieb Jim Jagielski : > > > > Most of

AW: ocsp stapling improvements

> -Ursprüngliche Nachricht- > Von: Stefan Eissing [mailto:stefan.eiss...@greenbytes.de] > Gesendet: Dienstag, 20. Juni 2017 13:40 > An: dev@httpd.apache.org > Betreff: Re: ocsp stapling improvements > > > > Am 12.06.2017 um 21:35 schrieb Ruediger Pluem : > > > > I guess the core mistake

AW: The drive for 2.4.26

> -Ursprüngliche Nachricht- > Von: Stefan Eissing [mailto:stefan.eiss...@greenbytes.de] > Gesendet: Dienstag, 6. Juni 2017 10:40 > An: dev@httpd.apache.org > Betreff: Re: The drive for 2.4.26 > > Proposed the patch as fix, since we did not see the behaviour pop up > again over the last d

AW: svn commit: r1707087 - /httpd/httpd/trunk/modules/debugging/mod_bucketeer.c

> /httpd/httpd/trunk/modules/debugging/mod_bucketeer.c > > On Wed, Apr 26, 2017 at 11:26 AM, Stefan Eissing > wrote: > > > >> Am 26.04.2017 um 11:14 schrieb Plüm, Rüdiger, Vodafone Group > : > >> > >> > >> > >>> -Ur

AW: svn commit: r1707087 - /httpd/httpd/trunk/modules/debugging/mod_bucketeer.c

> -Ursprüngliche Nachricht- > Von: Stefan Eissing [mailto:stefan.eiss...@greenbytes.de] > Gesendet: Mittwoch, 26. April 2017 10:55 > An: dev@httpd.apache.org > Betreff: Re: svn commit: r1707087 - > /httpd/httpd/trunk/modules/debugging/mod_bucketeer.c > > Eh, not really into mod_bucketeer

AW: AW: svn commit: r1707087 - /httpd/httpd/trunk/modules/debugging/mod_bucketeer.c

> -Ursprüngliche Nachricht- > Von: Jacob Champion [mailto:champio...@gmail.com] > Gesendet: Mittwoch, 26. April 2017 00:23 > An: dev@httpd.apache.org; Plüm, Rüdiger, Vodafone Group > > Betreff: Re: AW: svn commit: r1707087 - > /httpd/httpd/trunk/modules/debugging/mo

AW: svn commit: r1674661 - in /httpd/httpd/branches/2.4.x: ./ CHANGES STATUS modules/proxy/mod_proxy_wstunnel.c

I guess the patch is fine with one exception: Please do not "recycle" a configuration option setup explicitly for another module (flusher for mod_proxy_fdpass) for your patch. This only creates confusion. Please create a new one and document it. Regards Rüdiger > -Ursprüngliche Nachricht--

AW: [RFC] ?

+1 Regards Rüdiger > -Ursprüngliche Nachricht- > Von: Joe Orton [mailto:jor...@redhat.com] > Gesendet: Mittwoch, 8. März 2017 11:30 > An: dev@httpd.apache.org > Betreff: Re: [RFC] ? > > On Tue, Mar 07, 2017 at 11:52:17AM -0800, Jacob Champion wrote: > > On 02/28/2017 04:32 PM, Jacob Cha

AW: httpd 2.4.25, mpm_event, ssl: segfaults

> -Ursprüngliche Nachricht- > Von: Yann Ylavic [mailto:ylavic@gmail.com] > Gesendet: Donnerstag, 16. Februar 2017 11:35 > An: httpd-dev > Betreff: Re: httpd 2.4.25, mpm_event, ssl: segfaults > > On Thu, Feb 16, 2017 at 11:20 AM, Plüm, Rüdiger, Vo

AW: httpd 2.4.25, mpm_event, ssl: segfaults

> -Ursprüngliche Nachricht- > Von: Yann Ylavic [mailto:ylavic@gmail.com] > Gesendet: Donnerstag, 16. Februar 2017 10:49 > An: httpd-dev > Betreff: Re: httpd 2.4.25, mpm_event, ssl: segfaults > > Here are some SSL/core_write outputs (sizes) for me, with 2.4.x. > This is with a GET fo

AW: svn commit: r1707087 - /httpd/httpd/trunk/modules/debugging/mod_bucketeer.c

> -Ursprüngliche Nachricht- > Von: Yann Ylavic [mailto:ylavic@gmail.com] > Gesendet: Mittwoch, 15. Februar 2017 14:08 > An: httpd-dev > Betreff: Re: svn commit: r1707087 - > /httpd/httpd/trunk/modules/debugging/mod_bucketeer.c > > [with the patch] > > On Wed, Feb 15, 2017 at 2:07 P

AW: ssl_io_filter_output vs EOC

> -Ursprüngliche Nachricht- > Von: Yann Ylavic [mailto:ylavic@gmail.com] > Gesendet: Freitag, 3. Februar 2017 18:06 > An: httpd-dev > Betreff: ssl_io_filter_output vs EOC > > Besides metadata buckets, should the EOC semantic really apply to the > ssl output filter? > > It's not rea

  1   2   3   4   >