httpd

Checkout Tools
  • last updated 3 hours ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates

Changeset 1853418 is being indexed.

mod_rewrite doc rebuild
mod_rewrite.xml: add an example about override behavior

A user in PR 63051 was confused about the default behavior

of mod_rewrite (override) when merging two sections in the

directory context at the same nesting level. I was confused

as well, but after a quick look at the code I figured out that

RewriteOptions Inherit seems to solve the issue (naming is,

in this case, a bit counter intuitive).

Fix numbering
Move proposal to the right section.
Propose.
mod_proxy_http: rework the flushing strategy when forwarding the request body.

Since the forwarding of 100-continue (end to end) in r1836588, we depended on

reading all of the requested HUGE_STRING_LEN bytes to avoid the flushes, but

this is a bit fragile.

This commit introduces the new stream_reqbody_read() function which will try a

nonblocking read first and, if it fails with EAGAIN, will flush on the backend

side before blocking for the next client side read.

We can then use it in stream_reqbody_{chunked,cl}() to flush client forwarded

data only when necessary. This both allows "optimal" flushing and simplifies

code (note that spool_reqbody_cl() also makes use of the new function but not

its nonblocking/flush functionality, thus only for consistency with the two

others, simplification and common error handling).

Also, since proxy_http_req_t::flushall/subprocess_env::proxy-flushall are now

meaningless (and unused) on the backend side, they are renamed respectively to

prefetch_nonblocking/proxy-prefetch-nonblocking, and solely determine whether

to prefetch in nonblocking mode or not. These flags were trunk only and may

not be really useful if we decided to prefetch in nonblocking mode in any case,

but for 2.4.x the opt-in looks wise.

vote
vote
vote
Add comment
Follow up to r1847430.

- These flags are not for apr_dir_ function. Clarify comment.

- Initialize 'depth', especially when AP_DIR_FLAG_RECURSIVE is explicitelly required.

- Avoid an harmless over-allocation .

fr doc rebuild.

XML file fr doc update.

mod_rewrite doc rebuild
mod_rewrite.xml: add an example about override behavior

A user in PR 63051 was confused about the default behavior

of mod_rewrite (override) when merging two sections in the

directory context at the same nesting level. I was confused

as well, but after a quick look at the code I figured out that

RewriteOptions Inherit seems to solve the issue (naming is,

in this case, a bit counter intuitive). I hope that I added

a good clarification in the code, if not please amend it as

you think it's best!

Add an easy proposal
Propose
Restore "Changes with Apache 2.4.38" header.
update after backport
Merge of r1853133,r1853166 from trunk:

mod_ssl: Don't unset FIPS mode on restart unless it's forced by

configuration (SSLFIPS on) and not active by default in OpenSSL. PR 63136.

vote
* Vote
Fix a race condition.

Authentication with valid credentials could be refused in case of concurrent accesses from different users.

PR 63124 [Simon Kappel <simon.kappel axis.com>]

http2: mark tasks' pools.
Propose.
Follow up to r1853133: CHANGES entry.
mod_ssl: unset FIPS mode only if we set it.

If FIPS mode is set by default per openssl lib/module, we should not

unset it on restart or it might never be set again.

PR 63136

update transformations.
update for sync with English docs.

Translated by: Nilgün Belma Bugüner <nilgun belgeler.gen.tr>

Reviewed by: Orhan Berent <berent belgeler.gen.tr>

Use default DAVLockDB (statedir-relative) for 2.5.1+.