Keep Server Online
If you find the Apache Lounge, the downloads and overall help useful, please express your satisfaction with a donation.
or
A donation makes a contribution towards the costs, the time and effort that's going in this site and building.
Thank You! Steffen
Your donations will help to keep this site alive and well, and continuing building binaries. Apache Lounge is not sponsored.
| |
|
 Topic: Differences with mod_header |
|
| Author |
|
pbhq
Joined: 17 Mar 2013
Posts: 37
Location: Germany
|
 Posted: Mon 18 Feb '19 20:29 Post subject: Differences with mod_header |
 |
|
I noticed a small difference today between the Apache documentation and the practice at mod_header:
For example, I added a header like:
Header Set X-UA-Compatible "IE=8"
but Apache outputs an 'x-ua-compatible "IE=8"'-header instead of 'X-UA-Compatible "IE=8"'.
Any hints? |
|
| Back to top |
|
glsmith
Moderator
Joined: 16 Oct 2007
Posts: 2268
Location: Sun Diego, USA
|
| Posted: Tue 19 Feb '19 0:56 Post subject: |
|
|
Yes, a recursion when fixing something else.
I heard something about case-insensitive something before matching and this obviously got caught up in it.
It happened in 2.4.38.
Header always set X-Xss-Protection "1; mode=block"
2.4.37: X-Xss-Protection: 1; mode=block
2.4.38: x-xss-protection: 1; mode=block
I shot an email to dev@, we will see what they say. Personally, if I spend the time to capitalize it I want it to capitalize it. |
|
| Back to top |
|
pbhq
Joined: 17 Mar 2013
Posts: 37
Location: Germany
|
| Posted: Tue 19 Feb '19 18:11 Post subject: |
|
|
Thanks, I saw it.
No, the bug is independent of http/1.1 or http/2.0. That was my first guess ...  |
|
| Back to top |
|
|
|
|
|
|
