https://bz.apache.org/bugzilla/show_bug.cgi?id=57810
--- Comment #2 from Fred Morris <[email protected]> --- (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 > [...] > Since the URL is generated by service discovery I have no control over it. > The clients also behave consistently. The only way to get this to work > would be for apache to allow for this minor difference between the SNI and > HTTP hostnames. I believe that www.example.com and www.example.com. are equivalent. Apache already treats vhosts this way, it SHOULD (in the jargon of RFCs) ignore trailing dots for FQDN equivalence. My research indicates (most, in fact) clients are in error, because the SNI specification at least (not HTTP unfortunately) unequivocally calls for the trailing dot to be dropped. See bug 58007. -- You are receiving this mail because: You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
