Hi there,
Update: AFAICS, Debian/Ubuntu patches do nothing with NoProxy.
I've tested this on a different server (also an Ubuntu 22.04 LTS box
with Apache httpd 2.4.52) in a completely different network. The NoProxy
directive behaves slightly different on that host.
On that host, NoProxy
Hi there,
I've tracked this down to the sources now. Did not find any obvious errors.
Following line numbers are those of version/tag 2.4.52.
However, it seems like in mod_proxy.c, lines 1402 to 1405,
´direct_connect´ is constantly set to TRUE, if and only if NoProxy is
set to my local
Hello Yann,
thanks for your comments :)
Hello,
On Fri, May 5, 2023 at 9:22 AM Carsten Klein wrote:
Important(?) side note: through DNS the server can only resolve
local/intranet names and addresses. The DNS refuses to resolve
external/Internet names and addresses.
Unless NoProxy contains
Hello,
On Fri, May 5, 2023 at 9:22 AM Carsten Klein wrote:
>
> Important(?) side note: through DNS the server can only resolve
> local/intranet names and addresses. The DNS refuses to resolve
> external/Internet names and addresses.
Unless NoProxy contains only domain names (e.g.
