[Bug 58007] 400 Bad Request with fully qualified domain name over HTTPS

2015-06-08 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=58007 --- Comment #12 from Fred Morris consult...@m3047.net --- Wow. Well, there's a lot more to this than I reckoned... for the most part this discussion is beyond me. I do have one comment: any final dot should be ignored for comparison purposes.

[Bug 58007] 400 Bad Request with fully qualified domain name over HTTPS

2015-06-08 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=58007 --- Comment #13 from Fred Morris consult...@m3047.net --- See also: bug 57810 -- You are receiving this mail because: You are the assignee for the bug. - To unsubscribe,

[Bug 58007] 400 Bad Request with fully qualified domain name over HTTPS

2015-06-08 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=58007 --- Comment #15 from Fred Morris consult...@m3047.net --- It's not like compatibility with broken clients isn't a consideration: bug 56241 -- You are receiving this mail because: You are the assignee for the bug.

[Bug 57810] Should apache ignore difference in trailing dot between SNI and HTTP requests?

2015-06-08 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=57810 --- Comment #2 from Fred Morris consult...@m3047.net --- (In reply to Jean-Luc Duprat from comment #1) [...] [ssl:error] [pid 22158] AH02032: Hostname example.com. provided via SNI and hostname example.com provided via HTTP are different

[Bug 58007] 400 Bad Request with fully qualified domain name over HTTPS

2015-06-08 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=58007 --- Comment #14 from Fred Morris consult...@m3047.net --- Interesting: bug 56718 -- You are receiving this mail because: You are the assignee for the bug. - To unsubscribe,

[Bug 58007] 400 Bad Request with fully qualified domain name over HTTPS

2015-06-08 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=58007 --- Comment #8 from Yann Ylavic ylavic@gmail.com --- The SNI is compared against r-hostname, which is a parsed value of the original Host header (without the port, the trailing dots), supposedly SNI compatible... So I wonder if: 1) we

[Bug 58007] 400 Bad Request with fully qualified domain name over HTTPS

2015-06-08 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=58007 --- Comment #11 from Yann Ylavic ylavic@gmail.com --- Discussion about SNIed connections reuse moved to dev@. -- You are receiving this mail because: You are the assignee for the bug.

[Bug 58007] 400 Bad Request with fully qualified domain name over HTTPS

2015-06-08 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=58007 Yann Ylavic ylavic@gmail.com changed: What|Removed |Added CC||ylavic@gmail.com

[Bug 58007] 400 Bad Request with fully qualified domain name over HTTPS

2015-06-08 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=58007 --- Comment #9 from Stefan Eissing ste...@eissing.org --- It cannot be considered a bug when SNI and Host header differ. You cannot expect all requests on the same connection to have the same Host header either. Browsers will reuse TLS

[Bug 58007] 400 Bad Request with fully qualified domain name over HTTPS

2015-06-08 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=58007 --- Comment #10 from Yann Ylavic ylavic@gmail.com --- Hmm, so how are we supposed to handle a subsequent request on the same connection but for a different vhost with differents SSL parameters (eg. SSLProtocol, CipherSuite, ...),

[Bug 58007] 400 Bad Request with fully qualified domain name over HTTPS

2015-06-08 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=58007 Leho Kraav @lkraav l...@kraav.com changed: What|Removed |Added CC||l...@kraav.com --