As suggested in the wiki, did you set below during your tests. Let us know
your findings.
# Listen for virtual host requests on all IP addresses
NameVirtualHost *:443
# Go ahead and accept connections for these vhosts # from non-SNI clients
SSLStrictSNIVHostCheck off
Thanks,
Anil
> On Oct
Looks like it's not enabled on your listener. The global setting is not
correctly
inherited (and can lead to crashes because the merging is not handled
correctly
either.) I'd explicitly enable it in the first instance of each
you
are configuring.
The fix is non-trivial, feel free to file a bug
This is the only thing relevant to this:
[Thu Oct 17 15:49:26.886038 2019] [core:debug] [pid 30279] protocol.c(1335):
[client 172.31.38.27:59548] AH00566: request failed: malformed request line
Thanks !
> On 17 Oct 2019, at 15:52, William A Rowe Jr wrote:
>
> On Thu, Oct 17, 2019 at 9:04 AM
On Thu, Oct 17, 2019 at 2:06 AM Marian Ion wrote:
>
> Yes, that's why I set "SSLStrictSNIVHostCheck On" -> according to the
> documentation "If set to on in the default name-based virtual host,
> clients that are SNI unaware will not be allowed to access any virtual
> host".
> I set it in the
On Thu, Oct 17, 2019 at 9:04 AM David Tkacik <
dtka...@healthcoachinstitute.com> wrote:
>
> But when I try to connect I’m getting 400 Bad Request
>
Change your Apache LogLevel to 'debug' and repeat the attempt, examine the
error log and feel free to quote it here for further guidance.
Hey Guys,
I’m trying to make it work the AWS Network Loadbalancer’s ProxyProtocol V2 and
httpd.
I’m using the server version: Apache/2.4.39 (Amazon)
With mod_remoteip module loaded and enabled with the configuration directive
RemoteIPProxyProtocol On within the main server config.
What I was
On 17/10/2019 04:51, Anil Kumar P wrote:
> Is the client sending hostname header with the correct host, if not by
> default first vhost will be served.
Yes, that's why I set "SSLStrictSNIVHostCheck On" -> according to the
documentation "If set to on in the default name-based virtual host,
