apache2 doesn't compare SNI hostname against Host header case-insensitively
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Apache2 Web Server |
Unknown
|
Unknown
|
|||
apache2 (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Precise |
Fix Released
|
Medium
|
Unassigned |
Bug Description
[impact
Landscape client registration is fails with the following apache error message.
[Wed Mar 26 15:44:29 2014] [error] Hostname P122C-0-0-15680 provided via SNI and hostname p122c-0-0-15680 provided via HTTP are different.
it is because apache2 doesn't compare SNI hostname against Host header case-insensitively.
apache2 rejects connection request and returns 400 error code when the SNI doesn't match with requested.
http://
Therefore landscape client registration was failed.
- Precise 12.04 LTS
- apache2 : 2.2.22-1ubuntu1.4
[Test Case]
How reproducible is the problem?
( easily with the test case, intermittent, on every boot, etc)
1. Create self-signed SSL certificate file with upper case hostname
2. curl https:/
a. Actual Results - apache returns 400 Bad request error.
b. Expected Results - apache should return 200
[Regression Potential]
none, this has been merged into upstream and well tested.
[Other Info]
The same issue has been reported to apache upstream and the bug fix was applied at Aug 19 2013.
https:/
It looks like this patch is not applied to apache2 package for precise yet.
Changed in apache2 (Ubuntu Precise): | |
status: | New → Triaged |
importance: | Undecided → Medium |
@Ritesh
Thank you for the patch. Please could you confirm that this is verified fixed in Trusty?