Checkout Tools
  • last updated 1 hour ago
Constraints: committers
Constraints: files
Constraints: dates

Changeset 1843917 is being indexed.

Revert r1832567, r1843476, r1843478

Restore jorton's detection from r1831398, and portably redirect stderr

to capture and evaluate the available command list,

from either stdout (1.1.0 and later) or stderr (1.0.2 and prior).

md_acme_drive.c: remove unused variable

Compiling in maintainer mode leads to a failure

due to challenges_configured initialized but

not used. Removing it seems harmless, Stefan

please let me know if this is not the case.

XML update.

fr doc rebuild.

XML update.

fr doc rebuild.

XML updates.

first step in trying to make this test stop try to build curl. I have curl. The right one. With HTTP2 support. So why do we need to rebuild? Who knows. But now I need to figure out what to do about clients/Makefile*

propose "at maxrequestworkers" patch

On the trunk:

mod_md: eliminating compiler warnings re signedness and unused. Adding a APLOG_WARNING

when the only available ACME challenge is "tls-sni-01" since Let's Encrypt will

disable that completely beginning of 2019.

Adjusting version check to lowest httpd version that may support TLSv1.3

* This is addressed now
mpm_event: avoid AH00484 with idle threads

mpm_event: Stop issuing AH00484 "server reached MaxRequestWorkers..." when

there are still idle threads available. When there are less idle threads than

MinSpareThreads, issue new one-time message AH10159. Matches worker MPM.

Post 2.4.36 tag updates
Tag HEAD of 2.4.x as 2.4.36
Get ready to tag httpd 2.4.36
Better method... just check return status

Use this cli command

Note release
Merge r1843242 from trunk:

mod_brotli, mod_deflate: Restore the separate handling of 304 Not Modified

responses allowing these modules to properly set or fix-up the response

headers such as Vary or ETag.

This change follows up on r1837056 that disabled that special handling and

thus resulted in a potential violation of RFC7232, 4.1:

The server generating a 304 response MUST generate any of the following

header fields that would have been sent in a 200 (OK) response to the

same request: Cache-Control, Content-Location, Date, ETag, Expires,

and Vary.)


Submitted by: kotkov

Reviewed by: kotkov, ylavic, jim

Merge r1843426 from trunk:

mod_http2: adding defensive code for stream EOS handling, in case the request handler

missed to signal it the normal way (eos buckets). Addresses github issues,


Submitted by: icing

Reviewed by: icing, ylavic, jim

Merge r1839303, r1843290 from trunk:

These need to be signed longs... cast as needed.

Add CHANGES entry

Submitted by: jim, jailletc36

Reviewed by: jailletc36 (by inspection), ylavic, jim

approved backports

backport votes

No-op update to test buildbot config change.
Use SSL protocol versions set by -sslproto or determined by default.

adding proposal to backport h2 eos handling fix
Eliminating some advanced conversion and shadow declaration compiler warnings.

backport patch for h2 eos handling
    • ?