Re: Define variable in modules

It sounds like the desired change is , but there isn't a baked-in module revision field, not even a module release date that would be helpful here, so that isn't promising. IfDefine is a solution. Wouldn't solve this once and for all, for many use cases? Ship a patch for folks who want to rely

Re: --with-pcre Path Error configuring Apache 2.4.53-.54

A Rowe Jr wrote: > > The error below is acknowledged, and I worked out how it escaped my radar > (when pcre2-config exists, the current logic tolerates a broken > --with-pcre=/path, > finds the system pcre2-config or pcre-config, and if another dependency picks > the same path,

Re: --with-pcre Path Error configuring Apache 2.4.53-.54

The error below is acknowledged, and I worked out how it escaped my radar (when pcre2-config exists, the current logic tolerates a broken --with-pcre=/path, finds the system pcre2-config or pcre-config, and if another dependency picks the same path, the "desired" pcre is used and httpd assumes it

Re: svn commit: r1898399 - in /httpd/httpd/branches/2.4.x: ./ CHANGES CMakeLists.txt STATUS configure.in server/util_pcre.c

On Thu, Feb 24, 2022 at 4:18 PM wrote: > > Author: wrowe > Date: Thu Feb 24 22:18:42 2022 > New Revision: 1898399 > > URL: http://svn.apache.org/viewvc?rev=1898399=rev > Log: > Replace PCRE with PCRE2 where it is available > >*) Support PCRE2 with buffers reuse through Thread Local Storage. >

Re: opinion poll, stale issues

That's not entirely fair... We have done this periodically, by spamming the bugzilla entries with "please review under a current version and report back." Hearing no response after a month, it's trivial to close them for more info needed. Many aren't applicable to the current revision. The

Re: TLS neverbleed design

Considering this from the most extreme example, a hosting service where co-parties to using the server container are in contention to steal one anothers' identities, it seems the right answer is... Entirely isolate the network transport to the specific physical or SNI-based vhost in a distinct

Re: svn commit: r1897240 - in /httpd/httpd/trunk/server: main.c util_pcre.c

On Thu, Jan 20, 2022 at 10:33 AM Yann Ylavic wrote: > > On Thu, Jan 20, 2022 at 3:53 PM William A Rowe Jr wrote: > > > > pcre1 is very dangerous, on stack. pcre2 is highly cautioned against > > using stack for > > its arrays, by its author. We should heed the

Re: svn commit: r1897240 - in /httpd/httpd/trunk/server: main.c util_pcre.c

On Thu, Jan 20, 2022 at 5:09 AM wrote: > > Author: ylavic > Date: Thu Jan 20 11:09:34 2022 > New Revision: 1897240 > > URL: http://svn.apache.org/viewvc?rev=1897240=rev > Log: > ap_regex: Use Thread Local Storage (if efficient) to avoid allocations. > > PCRE2 wants an opaque context by providing

Re: svn commit: r1896976 - /httpd/httpd/branches/2.4.x/STATUS

On Wed, Jan 19, 2022 at 2:02 AM Ruediger Pluem wrote: > > On 1/18/22 11:03 PM, William A Rowe Jr wrote: > > On Tue, Jan 18, 2022 at 2:20 PM Ruediger Pluem wrote: > >> > >> On 1/18/22 8:54 PM, Yann Ylavic wrote: > >>> On Tue, Jan 18, 2022

Re: svn commit: r1896976 - /httpd/httpd/branches/2.4.x/STATUS

On Tue, Jan 18, 2022 at 2:20 PM Ruediger Pluem wrote: > > On 1/18/22 8:54 PM, Yann Ylavic wrote: > > On Tue, Jan 18, 2022 at 7:48 PM William A Rowe Jr > > wrote: > >> > >> Hi Joe, Yann and company, > >> > >> please consider this

Re: svn commit: r1896976 - /httpd/httpd/branches/2.4.x/STATUS

On Mon, Jan 17, 2022 at 6:38 PM Yann Ylavic wrote: > > On Mon, Jan 17, 2022 at 4:05 PM Joe Orton wrote: > > > > For 2.4.x I would argue it's better to keep a preference for 8.x over > > 10.x so that users aren't switched from one to the other across an > > upgrade - with some new performance

Re: svn commit: r1896976 - /httpd/httpd/branches/2.4.x/STATUS

On Mon, Jan 17, 2022, 09:37 Ruediger Pluem wrote: > > > On 1/17/22 4:05 PM, Joe Orton wrote: > > On Sun, Jan 16, 2022 at 03:35:15PM -0600, William A Rowe Jr wrote: > >> 4 day ago, you all saw this. 6 years ago, you all started using this on > trunk. > >> &

Re: svn commit: r1896976 - /httpd/httpd/branches/2.4.x/STATUS

t 7:28 AM Ruediger Pluem wrote: > > > > > > > > On 1/16/22 10:35 PM, William A Rowe Jr wrote: > > > 4 day ago, you all saw this. 6 years ago, you all started using this > on trunk. > > > > > > Don't know what I can to do help this along and ho

Re: svn commit: r1896976 - /httpd/httpd/branches/2.4.x/STATUS

4 day ago, you all saw this. 6 years ago, you all started using this on trunk. Don't know what I can to do help this along and honor the library author's wishes for all of us to walk away from the dead fork, and use the maintained fork. It's whatever it is, I'm out of here and removing the

Re: httpd test framework svn repo borked?

On Fri, Jan 14, 2022 at 4:08 AM Stefan Sperling wrote: > > On Thu, Jan 13, 2022 at 07:17:27PM -0600, William A Rowe Jr wrote: > > Thanks Stefan, it's attempting [locally] to replace a file, which was > > just created during the > > checkout (which might even be open). >

Re: Possible apr 1.7.1 showstopper from httpd test framework

On Fri, Jan 14, 2022 at 5:44 AM Joe Orton wrote: > > On Fri, Jan 14, 2022 at 11:37:35AM +0100, Ruediger Pluem wrote: > > > > On 1/14/22 6:47 AM, William A Rowe Jr wrote: > > > In addition to a broken release of brotli (where enc/dec don't specify > > >

Possible apr 1.7.1 showstopper from httpd test framework

In addition to a broken release of brotli (where enc/dec don't specify -lbrotlicommon, even on trunk, for openssl and other consumers to ferret out that binding), and lots of fun changes to build flags in curl 7.81 minor release (who does that?) there appears to be one test failure with date

Re: httpd test framework svn repo borked?

machine prereq. On Thu, Jan 13, 2022 at 3:28 PM Eric Covener wrote: > > On Thu, Jan 13, 2022 at 4:15 PM William A Rowe Jr wrote: > > > > I'm trying to work out how trunk on httpd test framework is busted on > > Windows, irrespective > > of using an msys2, sfl-ubuntu, o

Re: httpd test framework svn repo borked?

without complaint, while windows refuses. (At first I suspected a strange file perms issue or a conflicting file name case issue, but this is not the situation.) On Thu, Jan 13, 2022 at 3:34 PM Stefan Sperling wrote: > > On Thu, Jan 13, 2022 at 03:14:55PM -0600, William A Rowe Jr wrote: &

httpd test framework svn repo borked?

I'm trying to work out how trunk on httpd test framework is busted on Windows, irrespective of using an msys2, sfl-ubuntu, or older win32 native svn build. The problem always devolves to something like shown below; svn co -q -r 1896892 https://svn.apache.org/repos/asf/httpd/test/framework/trunk

Re: annou...@httpd.apache.org [moderator] missing

Stefan, thanks for RM'ing! On Fri, Oct 8, 2021 at 3:10 AM ste...@eissing.org wrote: > > The 2.4.51 announcement on annou...@httpd.apache.org did not make it, as seen > in the mailing list archives. > > I have no idea why not. Any moderator of that list here? Still no sign of it in

Re: pollset WAKEABLE

On Tue, Sep 28, 2021, 07:22 ste...@eissing.org wrote: > > > Am 28.09.2021 um 14:10 schrieb ste...@eissing.org: > > > >> Am 28.09.2021 um 14:04 schrieb Yann Ylavic : > >> > >> On Tue, Sep 28, 2021 at 1:08 PM ste...@eissing.org > wrote: > >>> > >>> Does anyone know which platforms do *not*

Re: APR 1.7.1 release?

I'm willing to RM APR and APR-util 1.7 releases. Would propose we set a date out 2 weeks, anything lingering needs to be finalized with the usual oversight no later than the 8th, and we tag on the 14th, announce on the 15th when the mirrors have caught up. That gives enough days for committers to

Re: [RESULT - PASS] Release httpd-2.4.48

This always happens, remember you must send announcement.*@a.o mail from an @a.o address. Which is extra confusing if you haven't set up the SMTP validation yet. On Tue, Jun 1, 2021 at 4:07 PM Christophe JAILLET wrote: > > Le 01/06/2021 à 03:07, William A Rowe Jr a écrit : > > Christ

Re: [RESULT - PASS] Release httpd-2.4.48

; > > > Here are the votes I have recorded during the thread: > (apologies if I missed someone) > PMC: > dferradal, jfclere, gbechis, jailletc36, jorton, rjung, steffenal, > ylavic > > Community and committers: > Noel Butler, Jan Ehrhardt, Cor

Re: Question about APR trunk and httpd ldap modules

On Sat, May 29, 2021 at 11:55 AM Roy T. Fielding wrote: > On May 28, 2021, at 9:59 AM, William A Rowe Jr > wrote: > > AIUI, as he remains a PMC member, the veto remains binding per Roy's > conclusion, whether it was made 9 weeks ago or 9 years ago. I do not, so > just

Re: Question about APR trunk and httpd ldap modules

On Thu, May 27, 2021 at 8:42 PM William A Rowe Jr wrote: > On Thu, May 27, 2021, 07:52 Eric Covener wrote: > >> On Thu, May 27, 2021 at 8:45 AM Rainer Jung >> wrote: >> >> > is my understanding correct, that even httpd trunk (and then also 2.4.x) >> &

Re: Question about APR trunk and httpd ldap modules

On Thu, May 27, 2021, 07:52 Eric Covener wrote: > On Thu, May 27, 2021 at 8:45 AM Rainer Jung > wrote: > > > is my understanding correct, that even httpd trunk (and then also 2.4.x) > > needs LDAP support in APR/APU to build mod_ldap and mod_authnz_ldap? > > > > So since we removed LDAP support

Re: [VOTE] Release httpd-2.4.48

The bandages back-ported from trunk resolved all the lua 5.4 issues... +1 from the peanut gallery for this candidate. On Mon, May 17, 2021, 16:37 Christophe JAILLET < christophe.jail...@wanadoo.fr> wrote: > Hi, all; > Please find below the proposed release tarball and signatures: >

Re: [VOTE] Release httpd-2.4.46

Following the announcement link, it isn't clear that https://httpd.apache.org/security/vulnerabilities_24.html fixes issues in 2.4.46. Should the fixed-in be promoted to the revision of Apache HTTP Server actually published (released) by the project? It almost reads like "fixed in 2.4.46-dev"

Re: Inexplicable sporadic 404 & 301 responses

Folks, the hostility in this exchange isn't appropriate, especially the later messages. On Mon, Aug 3, 2020 at 2:35 AM JunkYardMail1 wrote: > Getting sporadic not found (404) and redirects (301). These occur maybe > about 1 per 1000+ or so. > > The 404 responses are for existing content, and

Re: [VOTE] Release httpd-2.4.46

On Sat, Aug 1, 2020 at 9:13 AM Daniel Ruggeri wrote: > Hi, all; >Third time is a charm! Please find below the proposed release tarball > and signatures: > https://dist.apache.org/repos/dist/dev/httpd/ Just as a footnote to 2.4.46, as mentioned before mod_lua won't compile against the

Re: [VOTE] Release httpd-2.4.46

On Sat, Aug 1, 2020 at 9:13 AM Daniel Ruggeri wrote: > Hi, all; >Third time is a charm! 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: First impressions from OpenSSL 3.0.0 and httpd 2.4.45

On Sat, Aug 1, 2020 at 10:44 AM Rainer Jung wrote: > Hi there, > > during release testing for 2.4.45 I also built and tested using OpenSSL > 3.0.0alpha5 on the server. Overall first results are pretty good: > This is pretty awesome, thanks! Beyond the usual current packages, I'm also doing a

Re: [VOTE] Release httpd-2.4.45

On Thu, Jul 30, 2020 at 3:19 PM Daniel Ruggeri wrote: > > On 7/30/2020 2:41 PM, William A Rowe Jr wrote: > > On Thu, Jul 30, 2020 at 10:10 AM Jim Jagielski wrote: > >> >> > On Jul 30, 2020, at 5:55 AM, Christophe JAILLET < >> christophe.jail...@wana

Re: [VOTE] Release httpd-2.4.45

On Thu, Jul 30, 2020 at 10:10 AM Jim Jagielski wrote: > > > On Jul 30, 2020, at 5:55 AM, Christophe JAILLET < > christophe.jail...@wanadoo.fr> wrote: > > > > I wouldn't say it is a show stopper, but I thought that we had a travis > job for that. > > Apparently, it is on trunk only (see r1879370

Re: hardening mod_write and mod_proxy like mod_jk with servletnormalize

On Mon, Jul 20, 2020, 10:24 Ruediger Pluem wrote: > > > On 7/20/20 4:45 PM, Yann Ylavic wrote: > > On Thu, Jul 16, 2020 at 10:31 PM Eric Covener wrote: > >> > >> On Thu, Jul 16, 2020 at 3:31 PM Ruediger Pluem > wrote: > >>> > >>> > >>> > >>> On 6/24/20 1:27 PM, Eric Covener wrote: > > >

Re: iOS 14 / macOS 11 and HTTP/3 support

On Sun, Jun 28, 2020 at 5:53 AM Graham Leggett wrote: > On 27 Jun 2020, at 14:48, Luca Toscano wrote: > > > the challenges are the same one discussed in your previous email > > thread ( >

Re: Reject HTTP protocols >= 2.0 in ap_parse_request_line?

> On 6/18/20 12:09 AM, Roy T. Fielding wrote: > >> On Jun 8, 2020, at 12:56 AM, Ruediger Pluem > wrote: > >> > >> I came across the question if we should not reject HTTP protocols > >= 2.0 in the request line when we parse it > >> in ap_parse_request_line. > >> This does

Re: Building from svn on MacOS

On Mon, Apr 13, 2020 at 4:21 PM Christopher Schultz < ch...@christopherschultz.net> wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > William, > > >> I'm having some trouble building 2.4.x directly from svn. > >> > >> MacOS 10.14.6 (Mojave) > > > > I note you mentioned apr 1.7.0. If

Re: Building from svn on MacOS

On Mon, Apr 13, 2020, 11:41 Eric Covener wrote: > On Mon, Apr 13, 2020 at 12:19 PM Christopher Schultz > wrote: > > > > -BEGIN PGP SIGNED MESSAGE- > > Hash: SHA256 > > > > All, > > > > I'm having some trouble building 2.4.x directly from svn. > > > > MacOS 10.14.6 (Mojave) > > > > $

Re: Odd vulnerabilities_24.html output

On Sat, Apr 4, 2020 at 11:27 AM William A Rowe Jr wrote: > On Sat, Apr 4, 2020 at 10:23 AM Daniel Ruggeri > wrote: > >> Hi, all; >>I'm not sure what mechanism is used to generate >> https://httpd.apache.org/security/vulnerabilities_24.html from >> >>

Re: Odd vulnerabilities_24.html output

On Sat, Apr 4, 2020 at 10:23 AM Daniel Ruggeri wrote: > Hi, all; >I'm not sure what mechanism is used to generate > https://httpd.apache.org/security/vulnerabilities_24.html from > > https://svn.apache.org/repos/asf/httpd/site/trunk/content/security/vulnerabilities-httpd.xml > , >

Re: [VOTE] Release httpd-2.4.43

On Mon, Mar 30, 2020 at 8:41 PM Jan Ehrhardt wrote: > William A Rowe Jr in gmane.comp.apache.devel (Mon, 30 Mar 2020 09:01:07 > -0500): > >I'm making no attempt to build against the no-longer-supported msldap API > >nor openldap which doesn't support building on windows. >

Re: [VOTE] Release httpd-2.4.43

On Sun, Mar 29, 2020 at 8:26 AM Daniel Ruggeri wrote: > On 3/27/2020 12:58 PM, William A Rowe Jr wrote: > > On Fri, Mar 27, 2020 at 12:34 PM Steffen > <mailto:i...@apachelounge.com>> wrote: > > > > +1 All fine on Windows. > > > > > > Y

Re: OpenSSL 1.1.1e New EOF detection breaks session resumption

If you want to beat up your server in unusual ways, a good way to do this is to run it against https://www.ssllabs.com/ssltest/ from Qualsys with debug logging level throughout. I think you'll find we already sanitize all error results. On Fri, Mar 27, 2020 at 1:24 PM Steffen wrote: > > A

Re: [VOTE] Release httpd-2.4.43

On Fri, Mar 27, 2020 at 12:34 PM Steffen wrote: > +1 All fine on Windows. > Your's are still the .dsp based builds, right? I can confirm also on the CMake flavor.

Re: Help needed to test Windows builds in Travis

The https://github.com/appsuite/oss-httpd-build/tree/master/mak tree contains all the tooling we've used to generate convenience binaries. Makefile.build-win should be what you are looking for; we no longer test .dsp/.mak based builds, only CMake logic. But testing both while they remain

Re: httpd 2.4 and maintainer-mode

On Wed, Oct 9, 2019 at 3:42 PM Jim Jagielski wrote: > Just the issues w/ libxml comments: > > In file included from mod_xml2enc.c:38: > In file included from /usr/local/include/libxml2/libxml/encoding.h:31: > /usr/local/include/unicode/ucnv.h:1:1: error: // comments are not allowed > in this

Re: Migrate to git?

On Wed, Oct 9, 2019, 07:59 Michal Karm wrote: > On 10/08/2019 10:44 AM, Greg Stein wrote: > > On Tue, Oct 8, 2019 at 3:13 AM Joe Orton > > wrote: > > > > On Sat, Oct 05, 2019 at 04:09:34PM -0400, Jim Jagielski wrote: > > > Various PMCs have made their

Re: Cloudflare, Google Chrome, and Firefox Add HTTP/3 Support

On Fri, Sep 27, 2019 at 10:48 AM Eric Covener wrote: > On Fri, Sep 27, 2019 at 11:20 AM Helmut K. C. Tessarek > wrote: > > > > On 2019-09-27 03:00, Stefan Eissing wrote: > > > I know of no plans to implement HTTP/3 support in Apache httpd. > > > > I'm sorry, but this seems rather strange to me.

Re: Cloudflare, Google Chrome, and Firefox Add HTTP/3 Support

This answer \V/ (from Stefan) below. More explanation follows... The httpd project is entirely transparent. All development decisions occur on the email list you asked this question. Stefan himself stepped up to integrate Tatsuhiro's nghttp2 implementation into httpd (very successfully) so we

Re: Problem w/ Revision 1864435

This commit somehow missed my inbox (and wasn't quoted in your observations) http://svn.apache.org/viewvc?view=revision=1864435 Rainer, you observed in the commit notes; The GCC flag "-Wno-error=comment" introduced by r1855446 and

Re: SNI strict error logged as ssl:info, should be ssl:warm? (r1841455)

Lifting a post from the users discussion list. Should we revisit the error responses we make to demanding SSLRequireSSL, requiring SNI hostname matching, etc as 400 protocol violations, rather than "Permission Denied" with no further explanations? On Fri, Sep 13, 2019 at 8:25 AM William

Re: SNI strict error logged as ssl:info, should be ssl:warm? (r1841455)

On Fri, Sep 13, 2019 at 7:55 AM Tom Sommer wrote: > > On 2019-09-13 14:50, William A Rowe Jr wrote: > > > The same would likely apply to ssl traffic abuse. At this late date, > > clients connecting with 20 year old ssl semantics doesn't seem > > noteworthy. > > S

Re: SNI strict error logged as ssl:info, should be ssl:warm? (r1841455)

When we started rejecting more invalid traffic, e.g. malformed http request and header lines, we downgraded that all for plaintext traffic since there is no reason to collect garbage traffic reports in the normal error logging scenario. The same would likely apply to ssl traffic abuse. At this

Re: Trouble building 2.4.41 on Windows with CMake

his was > using 3.15.2 - the latest version. > > Thanks for fixing this. > > > On Fri, 30 Aug 2019 at 09:32, William A Rowe Jr > wrote: > >> However, it fixed it by ignoring most of the troubles... I have my IP >> unblocked, >> so I'm able to get some furthe

Re: Trouble building 2.4.41 on Windows with CMake

e trouble, and the fix has > sorted it out for me. > > On Fri, 30 Aug 2019 at 08:16, Stefan Eissing > wrote: > > > > Added to trunk in r1866119. > > Merged to 2.4.x in r1866121. > > > > Than

Re: Trouble building 2.4.41 on Windows with CMake

I have the immediate fix, can commit after lunch. The *right* fix is to iterate over the _require'ments list, I just took the shortcut of reducing this list to cmake (one of the most recent additions.) That patch will take a bit longer. On Thu, Aug 29, 2019 at 7:50 AM Stefan Eissing wrote: >

Breakage in httpd 2.4.39/windows/cmake?

Because of some trouble on another project, I wanted to recheck the current nghttp2 build between our mutual dependencies and httpd... and something isn't looking so healthy in the CMake build of the last release. (But I did answer my question, bazel shouldn't be failing to build nghttp2, it is

Re: Default log file locations

On Thu, Jun 27, 2019 at 4:24 PM Eric Covener wrote: > > From my perspective it would be advantageous to have Apache write to > > the terminal by default (i.e. no hardcoded log file locations) and > > allow to override this behavior via the Apache configuration file. > > > Is there any reason why

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

On Thu, Jun 27, 2019 at 2:06 PM Ruediger Pluem wrote: > > On 06/25/2019 10:39 AM, Plüm, Rüdiger, Vodafone Group wrote: > > > > Another related question: Do you think it would be beneficial if we > replace > > the apr_psprintf with apr_pstrcat in props.c as long as they only concat > strings

Re: svn commit: r1861542 - in /httpd/httpd/trunk: docs/manual/mod/mod_alias.xml modules/mappers/mod_alias.c

Hi Eric, Looking at this feature, and the new allowance effective June 2014, is this something we would want to toggle by envvar (in addition to or in lieu of a directive) similar to various gzip, caching, downgrade and particularly the redirect-carefully overrides? This seems like the sort of

Re: How can I dive into apache webserver source code

I'm confused, why are you building with gcc to a Microsoft OS platform target? What you are left with is a hybrid of bad posix-like thunks to native MS API. You COULD install SFU (the Ubuntu-on-Windows layer) and have a true posix environment, but be warned I'm seeing broken locking behavior

HTTP Protocol workshop notes

On Tue, Apr 9, 2019 at 11:48 AM Roy T. Fielding wrote: > > On Apr 9, 2019, at 3:30 AM, Stefan Eissing > wrote: > > > > I just did some tests with https://redbot.org/ (the site tester by Mark > Nottingham) against our server and it notifies of 2 things: > > > > 1. The "Keep-Alive" header is

Re: http://svn.apache.org/r1850745

To take this discussion all the way back to APR project's potential concerns... On Wed, Mar 13, 2019 at 8:03 AM Jim Jagielski wrote: > > > On Mar 13, 2019, at 8:56 AM, Nick Kew wrote: > > > >> On 13 Mar 2019, at 12:43, Jim Jagielski wrote: > >> > >> Is there anyone else building 2.4 on macOS

Re: http://svn.apache.org/r1850745

Just as a reminder of what r1850745 actually did, from an old discussion; On Wed, Jan 16, 2019 at 5:09 PM William A Rowe Jr wrote: > On Wed, Jan 16, 2019 at 3:54 PM Jim Jagielski wrote: > >> I'm sorry but I'm confused. The patch is as specific as you can get. It >> just adds

Re: http://svn.apache.org/r1850745

On Wed, Mar 13, 2019 at 8:04 AM Jim Jagielski wrote: > > Yeah, I also think it depends on the version of clang... previous versions > did not flag > > /usr/local/include/unicode/uenum.h:1:1: error: // comments are not > allowed in this language [-Werror,-Wcomment] > > as fatal errors. Just

Incomplete communications of OpenSSL 1.1.1 compatibility?

I was just updating PR 63212 and could not point the user at a top-level, definitive statement that they were trying to accomplish something very unwise and which they should have known better. Apparently there are few sources of this information. From http://httpd.apache.org/ ... Apache httpd

Re: http workshop

On Thu, Feb 14, 2019 at 2:36 PM Mark Thomas wrote: > On 14/02/2019 19:52, William A Rowe Jr wrote: > > On Mon, Jan 28, 2019 at 9:22 AM Stefan Eissing < > stefan.eiss...@greenbytes.de> > > wrote: > > > > >> The HTTP WS organisers expressed the wish

Re: http workshop

On Mon, Jan 28, 2019 at 9:22 AM Stefan Eissing wrote: > The HTTP Workshop is returning 2019 on April 2-4 in Amsterdam ( > https://github.com/httpworkshop/workshop2019). While I attended the last > three shops(?), I think it would be a good opportunity for someone else > from the team to go there

Re: Tidy up SVN commit lists

On Wed, Feb 13, 2019 at 4:12 PM sebb wrote: > HTTPD has several commit lists configured in asf-mailer.conf > > The default: > to_addr = c...@httpd.apache.org > > E) # can be dropped? > for_paths = httpd/httpd/win32-msi > to_addr = win32-msi-...@httpd.apache.org > The last commit for E) was in

Re: Close mbox-cvs@ mailing list?

On Sun, Jan 20, 2019 at 7:02 PM sebb wrote: > The mbox-cvs@httpd used to be used for mbox commit messages. > > However these now seem to be sent to cvs@ > > AFAICT there is no need to keep the list. > > Agreed? > Right call. The same is true of apreq-cvs@httpd, the commits should be going to

Re: [PATCH] mod_proxy: fix build without APR threads

On Tue, Jan 22, 2019 at 10:30 AM Stefan Sperling wrote: > On Tue, Jan 08, 2019 at 03:46:48PM +0100, Stefan Sperling wrote: > > mod_proxy fails to compile when APR doesn't have thread support. > > I don't know if this is supposed to be a supported configuration, > > but this problem did not exist

Sayonara httpd pmc

In private business, Greg Stein explicitly asked me "I no longer wish you to be part of this PMC" and as such, I've tendered, and my resignation was promptly accepted promptly by the committee chair. I look forward to working with you to solve occasional httpd bugs, but no longer speak to or

Re: svn commit: r1851557 - /httpd/httpd/branches/2.4.x/include/ap_release.h

On Thu, Jan 17, 2019 at 12:07 PM William A Rowe Jr wrote: > On Thu, Jan 17, 2019 at 12:03 PM Daniel Ruggeri > wrote: > >> >> We had a commit after the tag, > > > There are no tags. They are figments of your imagination :) When we > publish a tarball (even jus

Re: svn commit: r1851557 - /httpd/httpd/branches/2.4.x/include/ap_release.h

On Thu, Jan 17, 2019 at 12:03 PM Daniel Ruggeri wrote: > > We had a commit after the tag, There are no tags. They are figments of your imagination :) When we publish a tarball (even just under /dev/dist/), then we have a tag. Please svn rm the errant 2.4.39 tag. so I've updated only the

Re: [VOTE] Release httpd-2.4.28

An aside r.e. subversion; Just please don't do what gstein has warned us against. I've performed the ill-advised jump-over abandoned work in the past; svn rm ^/httpd/mod_foo/trunk svn cp ^/httpd/mod_foo/trunk@123456 ^/httpd/mod_foo/trunk attempting to drop activity between 123457 and

Re: svn commit: r1851557 - /httpd/httpd/branches/2.4.x/include/ap_release.h

One problem with scripts, they do just what they are told. You just tagged 2.4.39 as 2.4.38. Please revert to 2.4.38 and tag - until the tarballs are published to vote on, it's all development in svn history. On Thu, Jan 17, 2019 at 11:48 AM wrote: > Author: druggeri > Date: Thu Jan 17

Re: [VOTE] Release httpd-2.4.28

On Thu, Jan 17, 2019 at 11:44 AM Jim Jagielski wrote: > Note that simply changing the commit msg logs does not solve the problem. > There is, > in fact, no 2.4.38 tag at all. And I'm guessing we destroyed the "real" > 2.4.28 tag... :( Not destroyed, as ylavic observed. Nothing gets destroyed

Re: svn propchange: r1851549 - svn:log

Ahhh, true. Adjusted message appropriately. On Thu, Jan 17, 2019 at 11:44 AM Yann Ylavic wrote: > On Thu, Jan 17, 2019 at 6:36 PM wrote: > > > > Author: wrowe > > Revision: 1851549 > > Modified property: svn:log > > > > Modified: svn:log at Thu Jan 17 17:36:04 2019 > > >

Re: svn commit: r1850835 - /httpd/httpd/trunk/modules/aaa/mod_authn_dbm.c

On Thu, Jan 17, 2019 at 4:03 AM Joe Orton wrote: > On Wed, Jan 16, 2019 at 12:02:01PM -0600, William A Rowe Jr wrote: > > Doesn't this simply gloss over an underlying defect? > > > > [...] > > if (apr_dbm_fetch(f, key, ) == APR_SUCCESS && val.dptr) { >

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

On Wed, Jan 16, 2019 at 3:54 PM Jim Jagielski wrote: > I'm sorry but I'm confused. The patch is as specific as you can get. It > just adds the minimal option and JUST for filters and JUST if libxml2 is > part of the build. > Understood, but you might have overlooked the fact that changing

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

n: 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.net>: > > > > > > On Tue, Jan 15

Re: svn commit: r1850835 - /httpd/httpd/trunk/modules/aaa/mod_authn_dbm.c

Doesn't this simply gloss over an underlying defect? [...] if (apr_dbm_fetch(f, key, ) == APR_SUCCESS && val.dptr) { *value = apr_pstrmemdup(pool, val.dptr, val.dsize); } apr_dbm_close(f); return rv; } Shouldn't we capture and return the failure code from apr_dbm_fetch

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

On Tue, Jan 15, 2019 at 8:37 AM Jim Jagielski wrote: > > > On Jan 15, 2019, at 9:21 AM, Eric Covener wrote: > > > > On Tue, Jan 15, 2019 at 9:14 AM Jim Jagielski wrote: > >> > >> On Jan 9, 2019, at 7:41 PM, William A Rowe Jr > wrote: > >> >

Re: [NOTICE] Intent to T 2.4.28

On Tue, Jan 15, 2019 at 8:16 AM Jim Jagielski wrote: > Could I please get one more vote on adding in mod_socache_redis from > trunk... > This suggests one more adopter/reviewer. Has anyone in the community been using this module and can vouch for it? Anyone is welcome to share your votes here

Re: Is it interesting to add some filepath checks to apachectl -t ?

There should not be a 'warn' level emit for a non-existent directory. Unlike the DocumentRoot or Alias, which are searched, blocks describe protection. It's entirely reasonable to protect paths which aren't physically on the system at the current moment or in the current deployment. Something at

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

Hi Jim, Does CFLAGS -std=c99 solve your issue? It seems to work here. I'm building on the Fedora 29, largely frozen end-of-july. Reverting the patch below and toggling -std=c89 to -std=c99 in configure.in building all but two modules from trunk is building clean, and results in this command for

Re: svn commit: r1849177 - /httpd/httpd/trunk/CHANGES

On Wed, Dec 19, 2018 at 12:19 AM Christophe JAILLET < christophe.jail...@wanadoo.fr> wrote: > > I thought that now that 2.5.0 has been tagged, the history of 2.5.0+ > should not be axed when backported (i.e. this change would be in 2.5.1, > but is not in 2.5.0, which is tagged, so "does exist") >

Re: [PATCH] mod_deflate: hardcoded "%ld" -> APR_OFF_T_FMT

On Sun, Dec 16, 2018 at 7:27 AM Yann Ylavic wrote: > > Since it's logging only, it may be easier to cast to (long) each > total_in/out though. > Downcast? Why not upcast to apr_off_t and use the _FMT macro as first suggested?

Re: 2.4.38

On Sun, Nov 11, 2018 at 3:54 PM Barry Pollard wrote: > You only have to look at the past few attempts (scrapped versions) to > release apache to see the dangers in rush rush rush attitude. > > I’m assuming it’s a given that httpd should only release when ready to. I > don’t think any of the

Re: 2.4.38

On Fri, Nov 9, 2018 at 2:04 PM Graham Leggett wrote: > On 09 Nov 2018, at 17:51, Stefan Eissing > wrote: > > > So, the chance is high that releases we do will work for most of you. > > AND the chance is high that releases might break something for some of > you (hopefully a few). > > The chance

Re: Load balancing and load determination

On Thu, Nov 8, 2018 at 1:48 PM Jim Jagielski wrote: > I have a semi-working implementation that I'll be committing to trunk in a > bit... I'm confused. Semi-working would seem to be orthoganal to keeping trunk in a releasable state, but it depends on what you mean. But before you commit a

Re: [resolution] Stale BZ Bug Tracker reports

I clicked send on this note, before I saw the deluge. What we would not want is to hide closure notices to the cc recipients on the issue. We would not want to remove bugs@ from the issue itself. And anyone reconfirming a ticket is not stale is going to the bugs@ notification list. My only

Re: Exposing SSL certificates on SNI mismatch

On Fri, Nov 9, 2018 at 2:03 AM Ruediger Pluem wrote: > > On 11/08/2018 09:23 AM, Micha Lenk wrote: > > Hi all, > > > > I have a customer asking about whether the SSL handshake can be made to > fail in case the SNI from the "Client Hello" > > message doesn't match at all any server name of the

[resolution] Stale BZ Bug Tracker reports

Mass update completed. Search criteria; Version: 2.0-HEAD, 2.0.32, 2.0.35, 2.0.36, 2.0.39, 2.0.40, 2.0.42, 2.0.43, 2.0.44, 2.0.45, 2.0.46, 2.0.47, 2.0.48, 2.0.49, 2.0.50, 2.0.51, 2.0.52, 2.0.53, 2.0.54, 2.0.55, 2.0.58, 2.0.59, 2.0.61, 2.0.63, 2.0.64, 2.0.65, 2.1-HEAD, 2.2-HEAD, 2.2.0, 2.2.2,

Re: Stale BZ Bug Tracker reports

On Fri, Nov 2, 2018, 06:24 Luca Toscano Il giorno gio 1 nov 2018 alle ore 22:35 William A Rowe Jr > ha scritto: > > > > To keep this thread moving (additional feedback is welcomed and > appreciated)... > > Thanks a lot for this effort William, I really think that having

Re: Load balancing and load determination

On Mon, Nov 5, 2018 at 7:48 AM jean-frederic clere wrote: > On 30/10/2018 13:53, Jim Jagielski wrote: > > As some of you know, one of my passions and area of focus is > > on the use of Apache httpd as a reverse proxy and, as such, load > > balancing, failover, etc are of vital interest to me. >

Re: __attribute__

On Thu, Nov 1, 2018 at 3:31 PM Jim Jagielski wrote: > Since __attribute__ is used in various places in trunk and 2.4, is it safe > to assume that I can write something that requires __attribute__(packed)? No ... but surely you meant to write __attribute__((packed)) The real question is...

  1   2   3   4   5   6   7   8   9   10   >