Bug 60969 - HTTP/2 & Certificate path can lead to 421
Summary: HTTP/2 & Certificate path can lead to 421
Status: NEW
Alias: None
Product: Apache httpd-2
Classification: Unclassified
Component: mod_http2 (show other bugs)
Version: 2.4.25
Hardware: PC All
: P2 normal (vote)
Target Milestone: ---
Assignee: Apache HTTPD Bugs Mailing List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-04-11 09:54 UTC by Romain Lapoux
Modified: 2017-04-11 09:54 UTC (History)
0 users



Attachments

Note You need to log in before you can comment on or make changes to this bug.
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>