You would probably need to provide more information. What is the hostname in the URL? Are you entering https:// or http:// (or just the plain hostname) in the browser? (I.e. are you allowing the browser to do some magic with your request?) What CN/SANs does the certificate contain? How do you configure your Apache httpd VirtualHosts? And in which order? Is your Apache httpd configured to allow HTTP/2 (mod_http2) or just HTTP/1.x?
You can simulate a lot of scenarios using curl (to take Chrome out of the equation). So you might be able to figure out where your observed differences between 7.1 and 7.2 come from. The browser uses the hostname from the URL for a number of different purposes (simultaneously): - DNS host to IP resolution - HTTP Host: header - SSL SNI The Host: header and SNI should be identical in all practical situations. Using --resolve or --connect-to you can separate the DNS resolution from the actual hostname. There are also tons of options for specifying the TLS version or the HTTP protocol used. Note: I don’t use Chrome but I do use Brave Browser occasionally. After my upgrades to 7.2 I did not see any issues related to Apache httpd and TLS and some of the machines use a number of VirtualHosts with different certificates. Mike > Am 23.01.2023 um 17:12 schrieb Bambero <[email protected]>: > > > Hi, > > This is strange problem probably LibreSSL related. > > After upgrade OpenBSD to 7.2 windows clients using google chrome browser have > problems to connect to apache server. > Some requests are served correct, but periodically browser shows > NET::CERT_COMMON_NAME_INVALID and in server logs we can see: > > AH02645: Server name not provided via TLS extension (using default/first > virtual host), default > > There was no problem under 7.1. > > The problem occurs only when using google chrome browser (not chromium) under > windows. > > I compiled under 7.2 version of apache from 7.1 and from current - didn't > help. > OpenBSD builtin server works correct. > > Problem also submitted here: > https://bugs.chromium.org/p/chromium/issues/detail?id=1409224 > > Any ideas to solve the problem? > > Bambero -- Mike Fischer [email protected]
