Bug 60969

Summary: HTTP/2 & Certificate path can lead to 421
Product: Apache httpd-2 Reporter: Romain Lapoux <manus>
Component: mod_http2Assignee: Apache HTTPD Bugs Mailing List <bugs>
Status: NEW ---    
Severity: normal CC: huenig
Priority: P2    
Version: 2.4.25   
Target Milestone: ---   
Hardware: PC   
OS: All   

Description Romain Lapoux 2017-04-11 09:54:53 UTC
If we setup 2 virtualhosts using the same certificate but using different path for the certificate Apache send 421 during browsing between both virtualhost.
Certificate is for *.mydomain.com
What is working:
<VirtualHost *:443>
ServerName test1.mydomain.com
SSLEngine on
SSLCertificateFile /home/test1.mydomain.com/ssl.cert
SSLCertificateKeyFile /home/test1.mydomain.com/ssl.key
SSLCACertificateFile /home/test1.mydomain.com/ssl.ca
</VirtualHost>
<VirtualHost *:443>
ServerName test2.mydomain.com
SSLEngine on
SSLCertificateFile /home/test1.mydomain.com/ssl.cert
SSLCertificateKeyFile /home/test1.mydomain.com/ssl.key
SSLCACertificateFile /home/test1.mydomain.com/ssl.ca
</VirtualHost>
What is not working (leading 421 if navigate between both virtualhost):
<VirtualHost *:443>
ServerName test1.mydomain.com
SSLEngine on
SSLCertificateFile /home/test1.mydomain.com/ssl.cert
SSLCertificateKeyFile /home/test1.mydomain.com/ssl.key
SSLCACertificateFile /home/test1.mydomain.com/ssl.ca
</VirtualHost>
<VirtualHost *:443>
ServerName test2.mydomain.com
SSLEngine on
SSLCertificateFile /home/test2.mydomain.com/ssl.cert
SSLCertificateKeyFile /home/test2.mydomain.com/ssl.key
SSLCACertificateFile /home/test2.mydomain.com/ssl.ca
</VirtualHost>
Comment 1 Jonas H√ľnig 2019-12-11 13:00:36 UTC
Are there any plans for this? This would help us as well.