Hello,
mod_proxy includes a “ProxyPreserveHost” option, which causes the Host:
header to be preserved in requests to a backend.
httpd, though, seems to send a 421 response to any HTTP/1.1 request
whose Host header mismatches the SNI string.
Is ProxyPreserveHost, then,
On Fri, May 08, 2020 at 03:15:23PM +0200, Antony Stone wrote:
> On Friday 08 May 2020 at 15:00:07, Marc Haber wrote:
> > On Fri, May 08, 2020 at 02:01:03PM +0200, Antony Stone wrote:
> > > On Friday 08 May 2020 at 13:16:28, Marc Haber wrote:
> > > > I have a vhost in a https-only IPv6-only setup
On Friday 08 May 2020 at 15:00:07, Marc Haber wrote:
> On Fri, May 08, 2020 at 02:01:03PM +0200, Antony Stone wrote:
> > On Friday 08 May 2020 at 13:16:28, Marc Haber wrote:
> > > I have a vhost in a https-only IPv6-only setup and would like to make
> > > the web site hosted there reachable from
On Fri, May 08, 2020 at 02:01:03PM +0200, Antony Stone wrote:
> On Friday 08 May 2020 at 13:16:28, Marc Haber wrote:
> > I have a vhost in a https-only IPv6-only setup and would like to make
> > the web site hosted there reachable from the IPv4 Internet.
>
> Is the vhost capable of dealing with
On Friday 08 May 2020 at 13:16:28, Marc Haber wrote:
> Hi,
>
> I have a vhost in a https-only IPv6-only setup and would like to make
> the web site hosted there reachable from the IPv4 Internet.
Is the vhost capable of dealing with IPv4 queries if you can only manage to
get them to the
Hi,
I have a vhost in a https-only IPv6-only setup and would like to make
the web site hosted there reachable from the IPv4 Internet. On a
dual-homed host, I have sniproxy that forwards requests coming in via
IPv4 over IPv6 depending on the SNI header. The web server is directly
reachable from
> On 8 May 2020, at 07:28, Antonio Suárez Pozuelo
> wrote:
>
> Hi Nick,
>
> Your glass of wine was inspiring: just removed
>
>> ProxyHTMLCharsetOut * # Backend (Tomcat) charset is ISO-8859-1
>
> and the problem's gone!
OK, thanks for confirming it. I'm pretty sure now what's
Hi Nick,
Your glass of wine was inspiring: just removed
>ProxyHTMLCharsetOut * # Backend (Tomcat) charset is ISO-8859-1
and the problem's gone!
Also commented out
>ProxyHTMLMeta on
with no noticeable change in behaviour. As per the docs "turning ProxyHTMLMeta
