On Sun, 2012-02-19 at 09:04 -0500, Eric Covener wrote:
> You should be able to confirm in a packet capture or by logging
> %{SSL_TLS_SNI}e.
(after the first ";" you see the SNI host)
02/19/12 17:57:35> 129.187.131.227:443 188.174.212.187;
lcg-lrz-monitoring.grid.lrz.de /C=DE/O=GermanGrid/OU=LMU/
On Sun, 2012-02-19 at 09:04 -0500, Eric Covener wrote:
> > 2nd access:
> > I get an error, that no SNI hostname would have been provided, but still,
> > the ouput appears in the log file of the non-default name based vhost,
> > strange isn't it?
> No, Apache will still do normal vhost resolution.
B
> 2nd access:
> I get an error, that no SNI hostname would have been provided, but still,
> the ouput appears in the log file of the non-default name based vhost,
> strange isn't it?
>
No, Apache will still do normal vhost resolution. It's only mod_ssl
that will jump in the way if that occurred wi
Hi Eric.
Am 19.02.2012 01:21, schrieb Eric Covener:
What about LogLevel debug
Attached are fresh error logs with LogLevel debug.
From the default and non-default vhost (the later is where the actual
site, as you can see Icinga, runs).
For both cases split up in the 1st access (after I freshly
What about LogLevel debug or the access log?
What's in a decrypted packet trace?
-
The official User-To-User support forum of the Apache HTTP Server Project.
See http://httpd.apache.org/userslist.html> for more info.
To unsubscri
Hey.
This is actually from
https://issues.apache.org/bugzilla/show_bug.cgi?id=52703 but it seems
bug hunting is not welcomed there anymore, as I've already had to
experience in https://issues.apache.org/bugzilla/show_bug.cgi?id=52630
...
So I was redirected here to the list...
Well maybe so
