Re: [VOTE] broader RTC exception for 2.4.x CI changes

On Wed, Feb 15, 2023 at 2:49 PM Joe Orton wrote: > > Per my previous Travis is dead, long live GitHub actions. > > I propose to broaden the RTC exception in 2.4.x/STATUS to allow CI > config changes and scripts to be merged from trunk: > > Index: STATUS >

Re: [VOTE] broader RTC exception for 2.4.x CI changes

On 2/15/23 2:48 PM, Joe Orton wrote: > Per my previous Travis is dead, long live GitHub actions. > > I propose to broaden the RTC exception in 2.4.x/STATUS to allow CI > config changes and scripts to be merged from trunk: > > Index: STATUS >

Re: [VOTE] broader RTC exception for 2.4.x CI changes

On Wed, Feb 15, 2023 at 8:49 AM Joe Orton wrote: > > Per my previous Travis is dead, long live GitHub actions. > > I propose to broaden the RTC exception in 2.4.x/STATUS to allow CI > config changes and scripts to be merged from trunk: > > Index: STATUS >

[VOTE] broader RTC exception for 2.4.x CI changes

Per my previous Travis is dead, long live GitHub actions. I propose to broaden the RTC exception in 2.4.x/STATUS to allow CI config changes and scripts to be merged from trunk: Index: STATUS === --- STATUS (revision 1907679)

Re: CI status update: Travis out, GitHub Actions in

> Am 15.02.2023 um 11:51 schrieb Ruediger Pluem : > > > > On 2/15/23 11:43 AM, Joe Orton wrote: >> Support for Travis has now been dropped, so we are relying only on >> GitHub Actions for CI from today. >> >> There are some gaps in the GHA configuration compared to what we had >> running

Re: CI status update: Travis out, GitHub Actions in

On 2/15/23 11:43 AM, Joe Orton wrote: > Support for Travis has now been dropped, so we are relying only on > GitHub Actions for CI from today. > > There are some gaps in the GHA configuration compared to what we had > running in Travis: notably, we're currently only testing on the latest >

CI status update: Travis out, GitHub Actions in

Support for Travis has now been dropped, so we are relying only on GitHub Actions for CI from today. There are some gaps in the GHA configuration compared to what we had running in Travis: notably, we're currently only testing on the latest Ubuntu release, and nothing has been ported back to

Re: svn commit: r1907608 - in /httpd/httpd/trunk: CMakeLists.txt modules/dav/main/NWGNUmakefile modules/dav/main/config5.m4 modules/dav/main/mod_dav.c modules/dav/main/mod_dav.dsp modules/dav/main/mod

On 2/13/23 5:48 PM, m...@apache.org wrote: > Author: manu > Date: Mon Feb 13 16:48:35 2023 > New Revision: 1907608 > > URL: http://svn.apache.org/viewvc?rev=1907608=rev > Log: > Add MS-WDV support > > MS-WDV specification: > https://learn.microsoft.com/en-us/openspecs/windows_protocols/ms-wdv

Re: svn commit: r1907608 - in /httpd/httpd/trunk: CMakeLists.txt modules/dav/main/NWGNUmakefile modules/dav/main/config5.m4 modules/dav/main/mod_dav.c modules/dav/main/mod_dav.dsp modules/dav/main/mod

> > +static const char *mswdv_urlencode(request_rec *r, const char *str) (...) > Any reason why we cannot use an existing function like > ap_escape_path_segment here? MS-WDV section 2.2.3 quoted below says it needs to be percent-encoded as in RFC3986 section 2.1. How to do it with existing

Re: svn commit: r1907608 - in /httpd/httpd/trunk: CMakeLists.txt modules/dav/main/NWGNUmakefile modules/dav/main/config5.m4 modules/dav/main/mod_dav.c modules/dav/main/mod_dav.dsp modules/dav/main/mod

Le 13/02/2023 à 17:48, m...@apache.org a écrit : Author: manu Date: Mon Feb 13 16:48:35 2023 New Revision: 1907608 URL: http://svn.apache.org/viewvc?rev=1907608=rev Log: Add MS-WDV support MS-WDV specification: https://learn.microsoft.com/en-us/openspecs/windows_protocols/ms-wdv The changes

Re: svn commit: r1907608 - in /httpd/httpd/trunk: CMakeLists.txt modules/dav/main/NWGNUmakefile modules/dav/main/config5.m4 modules/dav/main/mod_dav.c modules/dav/main/mod_dav.dsp modules/dav/main/mod

On 2/13/23 5:48 PM, m...@apache.org wrote: > Author: manu > Date: Mon Feb 13 16:48:35 2023 > New Revision: 1907608 > > URL: http://svn.apache.org/viewvc?rev=1907608=rev > Log: > Add MS-WDV support > > MS-WDV specification: > https://learn.microsoft.com/en-us/openspecs/windows_protocols/ms-wdv

Bug report for Apache httpd-2 [2023/02/12]

+---+ | Bugzilla Bug ID | | +-+ | | Status: UNC=Unconfirmed NEW=New ASS=Assigned

Re: MS-WDV and other MS extensions

On 2/10/23 4:22 PM, Emmanuel Dreyfus wrote: > On Fri, Feb 10, 2023 at 04:15:16PM +0100, Ruediger Pluem wrote: >>> Do you suggests adding values to Options, or to create a DAVoptions >>> directive? >> >> I think DAVMSextis fine, but with an Options like syntax. > > Hence for now this? >

Re: MS-WDV and other MS extensions

On Fri, Feb 10, 2023 at 04:15:16PM +0100, Ruediger Pluem wrote: > > Do you suggests adding values to Options, or to create a DAVoptions > > directive? > > I think DAVMSextis fine, but with an Options like syntax. Hence for now this? DAVMSext +WDV -- Emmanuel Dreyfus m...@netbsd.org

Re: MS-WDV and other MS extensions

On 2/10/23 4:06 PM, Emmanuel Dreyfus wrote: > On Fri, Feb 10, 2023 at 09:53:47AM -0500, Eric Covener wrote: >> I like the third case with an all/on option. If it will need to be >> per-directory, maybe an Options like syntax would make sense? > > Do you suggests adding values to Options, or

Re: MS-WDV and other MS extensions

On Fri, Feb 10, 2023 at 09:53:47AM -0500, Eric Covener wrote: > I like the third case with an all/on option. If it will need to be > per-directory, maybe an Options like syntax would make sense? Do you suggests adding values to Options, or to create a DAVoptions directive? -- Emmanuel Dreyfus

Re: MS-WDV and other MS extensions

On 2/10/23 3:53 PM, Eric Covener wrote: > On Fri, Feb 10, 2023 at 9:17 AM Emmanuel Dreyfus wrote: >> >> Hello >> >> I am ready to commit MS-WDV support for mod_dav. There are many other >> MS extensions, and I just wonder if we should prepare to configure MS >> extensions one by one or as a

Re: MS-WDV and other MS extensions

On Fri, Feb 10, 2023 at 9:17 AM Emmanuel Dreyfus wrote: > > Hello > > I am ready to commit MS-WDV support for mod_dav. There are many other > MS extensions, and I just wonder if we should prepare to configure MS > extensions one by one or as a whole > > I mean, what directive makes more sense in

MS-WDV and other MS extensions

Hello I am ready to commit MS-WDV support for mod_dav. There are many other MS extensions, and I just wonder if we should prepare to configure MS extensions one by one or as a whole I mean, what directive makes more sense in httpd.conf? DAVMSext on (and if we add new MS extensions, this enables

Re: CPU affinity request

Nice proof of concept, but the code needs a serious porting effort to non-Linux platforms as well, and they’re all quirky in their own ways about this featureset. Doable tho. Joe Schaefer, Ph.D +1 (954) 253-3732 SunStar Systems, Inc. Orion - The Enterprise Jamstack Wiki

Bug report for Apache httpd-2 [2023/02/05]

+---+ | Bugzilla Bug ID | | +-+ | | Status: UNC=Unconfirmed NEW=New ASS=Assigned

CPU affinity request

Hi All, During httpd performance evaluation in Alibaba Cloud instance, I found httpd performance improved significantly after using “taskset” to set CPU affinity for httpd processes/threads, because it decreased the amount of CPU migrations. Performance improved 60% in arm instance g8y.2xlarge(8

Re: mod_wasm: Contributing Upstream to Apache

Yes, the usage of Wasm for filters makes a lot of sense. This is why I previously mentioned the Envoy’s proxy-wasm spec, which is essentially an ABI specification for running WebAssembly in proxies. Beyond Envoy, you can find similar approaches in

Re: Re: mod_wasm: Contributing Upstream to Apache

Part of the really cool things you'd like to have as an app-server author that knows the APR/APU/HTTPd runtime are subrequests, including the portions that interact with the filter API. I'm always writing home-grown app-specific SSI-ish filters via mod_perl to process application pages as

Re: mod_wasm: Contributing Upstream to Apache

Looking over the WASM Roadmap, it appears that they have a plan for multithreading within a single target language. That would allow you to fully support every silly GIL-addled language runtime out there, which would be very compelling. On Fri, Jan 27, 2023 at 1:33 PM Joe Schaefer wrote: > A

Re: mod_wasm: Contributing Upstream to Apache

A native interface outside of CGI compat for apreq would be a killer new feature, because it really finishes our vision for apreq as the one-HTML-spec-parser for all native apps, regardless of language choice. Of course this would be a new opt-in feature for target languages to take advantage of,

Re: mod_wasm: Contributing Upstream to Apache

Thanks Joe. You are correct, this initial implementation is the simplest one to get it off the ground. We plan to continue development and add the streaming functionality, which we know we will need for things like large PDF file generation or support for Proxy-Wasm. Yes, isolating language

RE: Re: mod_wasm: Contributing Upstream to Apache

Hi Eric, Thanks for the feedback. Though Wasm is relatively new it is being adopted by other HTTP-related projects, like NGINX and Envoy proxy and even ASF projects like APISIX. We want to contribute upstream to bring some of these new features to the Apache web server, similarly to how we are

Re: svn commit: r1907031 - /httpd/httpd/trunk/docs/manual/mod/mod_proxy.xml

On Fri, Jan 27, 2023 at 4:41 PM Eric Covener wrote: > > maybe we can duplicate that in the "basic examples" at the top of the page? Good point, did that in r1907035 (and linking to it in the note rather than copying the same example). I also added a deprecation warning to mod_proxy_wstunnel

Re: svn commit: r1907031 - /httpd/httpd/trunk/docs/manual/mod/mod_proxy.xml

maybe we can duplicate that in the "basic examples" at the top of the page? On Fri, Jan 27, 2023 at 10:31 AM wrote: > > Author: ylavic > Date: Fri Jan 27 15:30:46 2023 > New Revision: 1907031 > > URL: http://svn.apache.org/viewvc?rev=1907031=rev > Log: > docs: Better mod_proxy_wstunnel vs

Re: mod_wasm: Contributing Upstream to Apache

Still, the idea is wicked cool if mod_wasm really can isolate the Python, PHP, etc targets onto individual POSIX threads. Very exciting stuff for HTTP/2 Webapps. On Wed, Jan 25, 2023 at 4:31 AM Joe Schaefer wrote: > Looked at the PR- the IO is pretty primitive (no streaming anywhere). >

Re: mod_wasm: Contributing Upstream to Apache

Looked at the PR- the IO is pretty primitive (no streaming anywhere). Probably not fatal for Webapps, but it could use some better relations with the filter stack and bucket brigades. Joe Schaefer, Ph.D +1 (954) 253-3732 SunStar Systems, Inc. Orion - The Enterprise Jamstack Wiki

Re: mod_wasm: Contributing Upstream to Apache

Would be great to marry it to apreq, too. On Tue, Jan 24, 2023 at 4:04 PM Joe Schaefer wrote: > It is impossible to run mod_h2 without it or similar. > > On Tue, Jan 24, 2023 at 3:37 PM Eric Covener wrote: > >> > We are still very interested in contributing this module upstream and >> helping

Re: mod_wasm: Contributing Upstream to Apache

It is impossible to run mod_h2 without it or similar. On Tue, Jan 24, 2023 at 3:37 PM Eric Covener wrote: > > We are still very interested in contributing this module upstream and > helping to maintain it. Please, let us know what improvements or changes > would be needed for it to be

Re: mod_wasm: Contributing Upstream to Apache

> We are still very interested in contributing this module upstream and helping > to maintain it. Please, let us know what improvements or changes would be > needed for it to be considered ready for inclusion. As a pessimistic PMC member not caring about WASM or these languages, I worry that

Re: mod_wasm: Contributing Upstream to Apache

Hola! I wanted to update you on our progress since we have recently published new WebAssembly builds for several language runtimes, including: - PHP 8.1.11 and 8.2.0 - Python 3.11.1 - Ruby 3.2.0 With the inclusion of multi-module support in the mod_wasm v0.10.0 release, Apache can now serve

Bug report for Apache httpd-2 [2023/01/22]

+---+ | Bugzilla Bug ID | | +-+ | | Status: UNC=Unconfirmed NEW=New ASS=Assigned

Re: sporadic 500 errors with 2.4.55

Thanks for confirming, Steffen! > Am 19.01.2023 um 10:12 schrieb SteffenAL : > > No unnecessary 500 seen anymore in the access log. > > Steffen > >> --- Original message --- >> Subject: Re: sporadic 500 errors with 2.4.55 >> From: Stefan Eissing via dev >> To: >> Date: Wednesday,

Re: sporadic 500 errors with 2.4.55

No unnecessary 500 seen anymore in the access log. Steffen --- Original message --- Subject: Re: sporadic 500 errors with 2.4.55 From: Stefan Eissing via dev To: Date: Wednesday, 18/01/2023 21:06 Thanks for the fast confirmation. Added as r1906775 to trunk, proposed for backport to

Re: sporadic 500 errors with 2.4.55

Thanks for the fast confirmation. Added as r1906775 to trunk, proposed for backport to 2.4.x Kind Regards, Stefan > Am 18.01.2023 um 20:12 schrieb Helmut K. C. Tessarek : > > On 2023-01-18 13:40, Stefan Eissing via dev wrote: >> Thanks for the logs. That was really helpful. If you can build a

Re: sporadic 500 errors with 2.4.55

On 2023-01-18 13:40, Stefan Eissing via dev wrote: Thanks for the logs. That was really helpful. If you can build a 2.4.55 yourself, could you try the following patch? Yep, the patch fixed it. I don't see any 500 errors anymore. The 500 in the access log happens when a client RST (resets) a

Re: sporadic 500 errors with 2.4.55

Thanks for the logs. That was really helpful. If you can build a 2.4.55 yourself, could you try the following patch? h2-access-500-on-rst.diff Description: Binary data Analysis: The 500 in the access log happens when a client RST (resets) a stream before the response has really started.

Re: sporadic 500 errors with 2.4.55

Helmut, thanks for setting this up. If you can go a bit deeper and get me logs with "http2:trace2" that would be supberb. If you want to keep them out of the open, you can mail at ste...@eissing.org Thanks a lot! Stefan > Am 18.01.2023 um 17:00 schrieb Helmut K. C. Tessarek : > > On

Re: sporadic 500 errors with 2.4.55

On 2023-01-18 06:43, Stefan Eissing via dev wrote: In that case, maybe your could run the 2.4.55 mod_http2 with "LogLevel http2:debug" until some 500s show up. That would be very interesting to analyze. You can mail/link me such a log confidential atste...@eissing.org, if you like. I've setup

Re: sporadic 500 errors with 2.4.55

Am Wed, Jan 18, 2023 at 12:43:07PM +0100 schrieb Stefan Eissing via dev: > In that case, maybe your could run the 2.4.55 mod_http2 with "LogLevel > http2:debug" until some 500s show up. That would be very interesting to > analyze. > You can mail/link me such a log confidential at

Re: sporadic 500 errors with 2.4.55

> Am 18.01.2023 um 11:00 schrieb Andreas S. Kerber : > > Am Wed, Jan 18, 2023 at 10:18:56AM +0100 schrieb Stefan Eissing via dev: >> thanks for verifying that there is an issue. Would you be able to test a >> httpd 2.4.55 with a mod_http2 from 2.4.54? If that runs without trouble, we >> have

Re: sporadic 500 errors with 2.4.55

Am Wed, Jan 18, 2023 at 10:18:56AM +0100 schrieb Stefan Eissing via dev: > thanks for verifying that there is an issue. Would you be able to test a > httpd 2.4.55 with a mod_http2 from 2.4.54? If that runs without trouble, we > have the problem verified with the recent changes in the http2

Re: sporadic 500 errors with 2.4.55

Am Wed, Jan 18, 2023 at 10:19:39AM +0100 schrieb Ruediger Pluem: > Thanks. I understand it only happens with HTTP/2.0 not with other protocol > versions, correct? Anything in the error logs? Indeed only HTTP/2.0. No logged 500 errors since Jan 1st. Really started right after running 2.4.55. >

Re: sporadic 500 errors with 2.4.55

On 1/18/23 10:05 AM, Andreas S. Kerber wrote: > Am Wed, Jan 18, 2023 at 03:15:43AM -0500 schrieb Helmut K. C. Tessarek: >>> 2. As you see the 500 errors only in the access log are they only for >>> HTTP/2.0 or also for other protocol versions? > > I can confirm this too. I have a bunch of h2

Re: sporadic 500 errors with 2.4.55

Andreas, thanks for verifying that there is an issue. Would you be able to test a httpd 2.4.55 with a mod_http2 from 2.4.54? If that runs without trouble, we have the problem verified with the recent changes in the http2 implementation. Given that, could we check if we have a problem with the

Re: sporadic 500 errors with 2.4.55

Am Wed, Jan 18, 2023 at 03:15:43AM -0500 schrieb Helmut K. C. Tessarek: > > 2. As you see the 500 errors only in the access log are they only for > > HTTP/2.0 or also for other protocol versions? I can confirm this too. I have a bunch of h2 servers serving static content and a very small

Re: sporadic 500 errors with 2.4.55

These are all good questions. On 2023-01-18 02:04, Ruediger Pluem wrote: 1. As you suspect h2 have you tried running 2.4.55 without mod_http2? No. 2. As you see the 500 errors only in the access log are they only for HTTP/2.0 or also for other protocol versions? I believe so, but after

Re: sporadic 500 errors with 2.4.55

On 1/18/23 7:01 AM, Helmut K. C. Tessarek wrote: > Additional info: > > I reverted back to 2.4.54 and the errors are gone. It also seems that the > responses are snappier. The perf observation is > subjective of course. > > Without any proof I suspect that there is some sort of

Re: sporadic 500 errors with 2.4.55

Additional info: I reverted back to 2.4.54 and the errors are gone. It also seems that the responses are snappier. The perf observation is subjective of course. Without any proof I suspect that there is some sort of contention/lock issue with h2 that might also result in a 500 now and then

sporadic 500 errors with 2.4.55

After I have upgraded to 2.4.55, I get internal 500 errors now and then. The strange thing is that they do not show up in the error log, but only in the access log. Another weird thing is that they seem random and happen with random files, like the favicon.ico I don't do any redirects so

Re: [httpd-site] branch main updated: publishing release httpd-2.4.55

On 2023-01-17 18:59, Eric Covener wrote: Something is still subtly wrong here, the 2.4.55 section only has 1 entry instead of 3. Will chat about it on #httpd on ASF slack. We have addressed the immediate issue, and the page is rendering as intended, but we'll have to talk to the folks in

Re: mod_wasm: Contributing Upstream to Apache

Hola! Did anyone have the chance to take a look to the latest PR? It would be great to receive any additional feedback with the upstream contribution in mind. We are making great progress in our end, now focused on porting more PHP apps for mod_wasm, and support for new language runtimes such

Re: [httpd-site] branch main updated: publishing release httpd-2.4.55

Something is still subtly wrong here, the 2.4.55 section only has 1 entry instead of 3. Will chat about it on #httpd on ASF slack. On Tue, Jan 17, 2023 at 12:17 PM Daniel Gruno wrote: > > I have patched the system to deal with the inconsistencies, but those > should really be looked at. There

Re: [httpd-site] branch main updated: publishing release httpd-2.4.55

I have patched the system to deal with the inconsistencies, but those should really be looked at. There seems to be a mix of "timeline" entries that are not consistent throughout the dir (even when accounting for v4.0 vs v5.0 CVE data), and those were throwing spanners into the build process.

Re: [httpd-site] branch main updated: publishing release httpd-2.4.55

Humbedooh is helping. Note that the SVN repo is dead content, real content is in g...@github.com:/apache/httpd-site On Tue, Jan 17, 2023 at 11:39 AM Eric Covener wrote: > > I think it's > https://svn.apache.org/repos/asf/httpd/site/trunk/content/security/cvejsontohtml.py > it hasn't been

Re: [httpd-site] branch main updated: publishing release httpd-2.4.55

I think it's https://svn.apache.org/repos/asf/httpd/site/trunk/content/security/cvejsontohtml.py it hasn't been updated for the V5 JSON format, I misinterpreted Mark's mail. I will try to make it tolerant of both. On Tue, Jan 17, 2023 at 11:29 AM Ruediger Pluem wrote: > > > > On 1/17/23 5:16

Re: [httpd-site] branch main updated: publishing release httpd-2.4.55

On 1/17/23 5:16 PM, cove...@apache.org wrote: > This is an automated email from the ASF dual-hosted git repository. > > covener pushed a commit to branch main > in repository https://gitbox.apache.org/repos/asf/httpd-site.git > > > The following commit(s) were added to refs/heads/main by

Re: [VOTE] Release httpd-2.4.55-rc1 as httpd-2.4.55

Vote, passes w/ 6 binding +1 and no -1: +1 covener, jorton, icing, ylavic, jim, gbechis I will continue the release process tomorrow. On Tue, Jan 10, 2023 at 8:40 AM Eric Covener wrote: > > Hi all, > > Please find below the proposed release tarball and signatures: > >

Bug report for Apache httpd-2 [2023/01/15]

+---+ | Bugzilla Bug ID | | +-+ | | Status: UNC=Unconfirmed NEW=New ASS=Assigned

Re: svn commit: r1906618 - /httpd/httpd/branches/2.2.x/docs/manual/rewrite/intro.xml

On Thu, 2023-01-12 at 16:30 +0100, Ruediger Pluem wrote: > > $ wget http://localhost/games > > /home/rbowen/devel/presentations/puzzles is a directory, correct? > If yes, you get a redirect by mod_dir > Try making puzzles a file. > > > > > It looks like it works as intended, but then for some

Re: svn commit: r1906618 - /httpd/httpd/branches/2.2.x/docs/manual/rewrite/intro.xml

On 1/12/23 4:23 PM, rbo...@rcbowen.com wrote: > On Thu, 2023-01-12 at 09:59 -0500, rbo...@rcbowen.com wrote: >> >> I'll dig deeper on this. >> > > What I'm seeing is not making much sense to me. > > With: > > RewriteRule "^/games$" "/puzzles" > > I'm getting the following behavior: > >>> >

Re: svn commit: r1906618 - /httpd/httpd/branches/2.2.x/docs/manual/rewrite/intro.xml

DirectorySlash from mod_dir. Maybe with [PT] it would redirect to /puzzles/ (if it's on disk) or skip it. On Thu, Jan 12, 2023 at 10:23 AM wrote: > > On Thu, 2023-01-12 at 09:59 -0500, rbo...@rcbowen.com wrote: > > > > I'll dig deeper on this. > > > > What I'm seeing is not making much sense to

Re: svn commit: r1906618 - /httpd/httpd/branches/2.2.x/docs/manual/rewrite/intro.xml

On Thu, 2023-01-12 at 09:59 -0500, rbo...@rcbowen.com wrote: > > I'll dig deeper on this. > What I'm seeing is not making much sense to me. With: RewriteRule "^/games$" "/puzzles" I'm getting the following behavior: >> [Thu Jan 12 10:12:26.174426 2023] [rewrite:trace2] [pid 615418:tid

Re: svn commit: r1906618 - /httpd/httpd/branches/2.2.x/docs/manual/rewrite/intro.xml

On Wed, 2023-01-11 at 19:36 -0800, Roy T. Fielding wrote: > I am pretty sure that this change makes the example incorrect. > > That regex is not supposed to match "/foo/" (even if one might > want to do that for directory examples, this particular example > is not about directories). /foo is the

Re: [VOTE] Release httpd-2.4.55-rc1 as httpd-2.4.55

Not a showstopper, but: srclib/apr/configure was again generated with autoconf 2.70+ (2.71). This triggers a bug which is fixed in APR 1.7.x head, but the fix has not been released as there was not APR release vor almost 4 years now. Since the bundled APR/APU are not actually part of the

Re: [VOTE] Release httpd-2.4.55-rc1 as httpd-2.4.55

Le 11/01/2023 à 10:05, Stefan Eissing via dev a écrit : Nearly all mod_tls in error (likely something missing in my conf) Not here. Do you have any more information on those failures? Still don't have time to spend some minutes on it, but: configure:35461: checking whether to enable

Re: svn commit: r1906618 - /httpd/httpd/branches/2.2.x/docs/manual/rewrite/intro.xml

I am pretty sure that this change makes the example incorrect. That regex is not supposed to match "/foo/" (even if one might want to do that for directory examples, this particular example is not about directories). /foo is the whole path. If a directory example is desired, perhaps a new

Re: [VOTE] Release httpd-2.4.55-rc1 as httpd-2.4.55

> On Jan 10, 2023, at 8:40 AM, Eric Covener wrote: > > Hi all, > > Please find below the proposed release tarball and signatures: > > https://dist.apache.org/repos/dist/dev/httpd/ > > I would like to call a VOTE over the next few days to release > this candidate tarball httpd-2.4.55-rc1 as

Re: [VOTE] Release httpd-2.4.55-rc1 as httpd-2.4.55

On 1/10/23 14:40, Eric Covener wrote: Hi all, Please find below the proposed release tarball and signatures: https://dist.apache.org/repos/dist/dev/httpd/ I would like to call a VOTE over the next few days to release this candidate tarball httpd-2.4.55-rc1 as 2.4.55 +1 for release looks fine

Re: [VOTE] Release httpd-2.4.55-rc1 as httpd-2.4.55

> Am 11.01.2023 um 15:50 schrieb Yann Ylavic : > > On Wed, Jan 11, 2023 at 10:10 AM Stefan Eissing via dev > wrote: >> >>> Am 10.01.2023 um 22:39 schrieb Christophe JAILLET >>> : >>> >>> 1 issue with pytest: >>> test/modules/http2/test_600_h2proxy.py .F >>> (details at the end of

Re: [VOTE] Release httpd-2.4.55-rc1 as httpd-2.4.55

On Wed, Jan 11, 2023 at 9:51 AM Yann Ylavic wrote: > > On Wed, Jan 11, 2023 at 10:10 AM Stefan Eissing via dev > wrote: > > > > > Am 10.01.2023 um 22:39 schrieb Christophe JAILLET > > > : > > > > > > 1 issue with pytest: > > > test/modules/http2/test_600_h2proxy.py .F > > > (details

Re: [VOTE] Release httpd-2.4.55-rc1 as httpd-2.4.55

On Wed, Jan 11, 2023 at 10:10 AM Stefan Eissing via dev wrote: > > > Am 10.01.2023 um 22:39 schrieb Christophe JAILLET > > : > > > > 1 issue with pytest: > > test/modules/http2/test_600_h2proxy.py .F > > (details at the end of the mail) > > > > Don't know if expected or not. Some

Re: [VOTE] Release httpd-2.4.55-rc1 as httpd-2.4.55

On Tue, Jan 10, 2023 at 2:41 PM Eric Covener wrote: > > I would like to call a VOTE over the next few days to release > this candidate tarball httpd-2.4.55-rc1 as 2.4.55: +1 on Debian 11 & 12, thanks Eric for RMing. Regards; Yann.

Re: [VOTE] Release httpd-2.4.55-rc1 as httpd-2.4.55

I am +1 on my macOS testing of the candidate. Addressing the findings from Christophe: > Am 10.01.2023 um 22:39 schrieb Christophe JAILLET > : > > Le 10/01/2023 à 14:40, Eric Covener a écrit : >> Hi all, >> Please find below the proposed release tarball and signatures: >>

Re: [VOTE] Release httpd-2.4.55-rc1 as httpd-2.4.55

Le 10/01/2023 à 14:40, Eric Covener a écrit : Hi all, Please find below the proposed release tarball and signatures: https://dist.apache.org/repos/dist/dev/httpd/ I would like to call a VOTE over the next few days to release this candidate tarball httpd-2.4.55-rc1 as 2.4.55: [ ] +1: It's not

Re: [VOTE] Release httpd-2.4.55-rc1 as httpd-2.4.55

Re: [VOTE] Release httpd-2.4.55-rc1 as httpd-2.4.55

On Tue, Jan 10, 2023 at 10:21:55AM -0500, Eric Covener wrote: > On Tue, Jan 10, 2023 at 10:17 AM Giovanni Bechis wrote: ... > > In file included from /usr/include/openssl/asn1.h:27, > > from /usr/include/openssl/rsa.h:21, > > from ab.c:169: > >

Re: [VOTE] Release httpd-2.4.55-rc1 as httpd-2.4.55

On Tue, Jan 10, 2023 at 10:17 AM Giovanni Bechis wrote: > > On Tue, Jan 10, 2023 at 08:40:52AM -0500, Eric Covener wrote: > > Hi all, > > > > Please find below the proposed release tarball and signatures: > > > > https://dist.apache.org/repos/dist/dev/httpd/ > > > > I would like to call a VOTE

Re: [VOTE] Release httpd-2.4.55-rc1 as httpd-2.4.55

On Tue, Jan 10, 2023 at 08:40:52AM -0500, Eric Covener wrote: > Hi all, > > Please find below the proposed release tarball and signatures: > > https://dist.apache.org/repos/dist/dev/httpd/ > > I would like to call a VOTE over the next few days to release > this candidate tarball

Re: [VOTE] Release httpd-2.4.55-rc1 as httpd-2.4.55

On Tue, Jan 10, 2023 at 08:40:52AM -0500, Eric Covener wrote: > Hi all, > > Please find below the proposed release tarball and signatures: > > https://dist.apache.org/repos/dist/dev/httpd/ > > I would like to call a VOTE over the next few days to release > this candidate tarball

Re: [VOTE] Release httpd-2.4.55-rc1 as httpd-2.4.55

On Tue, Jan 10, 2023 at 8:40 AM Eric Covener wrote: > > Hi all, > > Please find below the proposed release tarball and signatures: > > https://dist.apache.org/repos/dist/dev/httpd/ > > I would like to call a VOTE over the next few days to release > this candidate tarball httpd-2.4.55-rc1 as

[VOTE] Release httpd-2.4.55-rc1 as httpd-2.4.55

Hi all, Please find below the proposed release tarball and signatures: https://dist.apache.org/repos/dist/dev/httpd/ I would like to call a VOTE over the next few days to release this candidate tarball httpd-2.4.55-rc1 as 2.4.55: [ ] +1: It's not just good, it's good enough! [ ] +0: Let's have

Re: svn commit: r1906487 - /httpd/httpd/trunk/modules/dav/main/util.c

On 1/10/23 12:10 PM, Joe Orton wrote: > On Tue, Jan 10, 2023 at 07:30:37AM +0100, Ruediger Pluem wrote: >> On 1/9/23 5:16 PM, Joe Orton wrote: >>> It seems consistent with other error cases to return straight away, but >>> I'm not following the second part, can you explain more? An 'N' >>>

Re: svn commit: r1906487 - /httpd/httpd/trunk/modules/dav/main/util.c

On Tue, Jan 10, 2023 at 07:30:37AM +0100, Ruediger Pluem wrote: > On 1/9/23 5:16 PM, Joe Orton wrote: > > It seems consistent with other error cases to return straight away, but > > I'm not following the second part, can you explain more? An 'N' > > followed by whitespace should be caught and

Re: svn commit: r1903677 - in /httpd/httpd/trunk: changes-entries/ docs/manual/mod/ modules/md/ test/modules/md/

> Am 09.01.2023 um 22:14 schrieb Christophe JAILLET > : > > Le 25/08/2022 à 16:00, ic...@apache.org a écrit : >> Author: icing >> Date: Thu Aug 25 14:00:13 2022 >> New Revision: 1903677 >> URL: http://svn.apache.org/viewvc?rev=1903677=rev >> Log: >> mod_md v2.4.19 from github sync >> *)

Re: svn commit: r1906487 - /httpd/httpd/trunk/modules/dav/main/util.c

On 1/9/23 5:16 PM, Joe Orton wrote: > On Mon, Jan 09, 2023 at 04:47:33PM +0100, Ruediger Pluem wrote: >> On 1/9/23 1:01 PM, jor...@apache.org wrote: >>> Author: jorton >>> Date: Mon Jan 9 12:01:56 2023 >>> New Revision: 1906487 >>> >>> URL: http://svn.apache.org/viewvc?rev=1906487=rev >>> Log:

Re: svn commit: r1903677 - in /httpd/httpd/trunk: changes-entries/ docs/manual/mod/ modules/md/ test/modules/md/

Le 25/08/2022 à 16:00, ic...@apache.org a écrit : Author: icing Date: Thu Aug 25 14:00:13 2022 New Revision: 1903677 URL: http://svn.apache.org/viewvc?rev=1903677=rev Log: mod_md v2.4.19 from github sync *) mod_md: a new directive `MDStoreLocks` can be used on cluster setups with a

Re: svn commit: r1906487 - /httpd/httpd/trunk/modules/dav/main/util.c

On Mon, Jan 09, 2023 at 04:47:33PM +0100, Ruediger Pluem wrote: > On 1/9/23 1:01 PM, jor...@apache.org wrote: > > Author: jorton > > Date: Mon Jan 9 12:01:56 2023 > > New Revision: 1906487 > > > > URL: http://svn.apache.org/viewvc?rev=1906487=rev > > Log: > > * modules/dav/main/util.c

Re: stable branch

On Mon, Jan 9, 2023 at 10:35 AM Ruediger Pluem wrote: > > > > On 1/9/23 3:54 PM, Emmanuel Dreyfus wrote: > > On Mon, Jan 09, 2023 at 09:37:37AM -0500, Eric Covener wrote: > >> svn relocate http://svn.apache.org https://svn.apache.org > > > > That did it! I made the commit, but someone

Re: svn commit: r1906487 - /httpd/httpd/trunk/modules/dav/main/util.c

On 1/9/23 1:01 PM, jor...@apache.org wrote: > Author: jorton > Date: Mon Jan 9 12:01:56 2023 > New Revision: 1906487 > > URL: http://svn.apache.org/viewvc?rev=1906487=rev > Log: > * modules/dav/main/util.c (dav_process_if_header): Fix error > path for "Not" prefix parsing. > > Modified: >

Re: stable branch

On 1/9/23 3:54 PM, Emmanuel Dreyfus wrote: > On Mon, Jan 09, 2023 at 09:37:37AM -0500, Eric Covener wrote: >> svn relocate http://svn.apache.org https://svn.apache.org > > That did it! I made the commit, but someone knowledgable should > probably check I did not break something Looks good.

Re: svn commit: r1906494 - in /httpd/httpd/branches/2.4.x: ./ CHANGES STATUS docs/manual/expr.xml docs/manual/mod/mod_authn_core.xml modules/aaa/mod_authn_core.c

On Mon, Jan 9, 2023 at 10:11 AM Ruediger Pluem wrote: > > > > On 1/9/23 2:16 PM, cove...@apache.org wrote: > > Author: covener > > Date: Mon Jan 9 13:16:50 2023 > > New Revision: 1906494 > > > > URL: http://svn.apache.org/viewvc?rev=1906494=rev > > Log: > > Merge r1663123, r1670431 from trunk: >

Re: svn commit: r1906494 - in /httpd/httpd/branches/2.4.x: ./ CHANGES STATUS docs/manual/expr.xml docs/manual/mod/mod_authn_core.xml modules/aaa/mod_authn_core.c

On 1/9/23 2:16 PM, cove...@apache.org wrote: > Author: covener > Date: Mon Jan 9 13:16:50 2023 > New Revision: 1906494 > > URL: http://svn.apache.org/viewvc?rev=1906494=rev > Log: > Merge r1663123, r1670431 from trunk: > > mod_authn_core: Add expression support to AuthName and AuthType.

Re: stable branch

On Mon, Jan 09, 2023 at 09:37:37AM -0500, Eric Covener wrote: > svn relocate http://svn.apache.org https://svn.apache.org That did it! I made the commit, but someone knowledgable should probably check I did not break something -- Emmanuel Dreyfus m...@netbsd.org

Re: stable branch

On Mon, Jan 9, 2023 at 9:23 AM Emmanuel Dreyfus wrote: > > On Mon, Jan 09, 2023 at 08:05:30AM -0500, Eric Covener wrote: > > Yes. Most times, the person who proposed it does the final backport. > > Sometimes, the last person to vote or someone preparing a release will > > apply it. > > Um, sorry

<    5   6   7   8   9   10   11   12   13   14   >