logo
Apache Lounge
Webmasters

 


About

Forum Index Downloads Search Register Log in  RSS Apache Lounge
 


Keep Server Online

If you find the Apache Lounge, the downloads and overall help useful, please express your satisfaction with a donation.

or

Bitcoin

A donation makes a contribution towards the costs, the time and effort that's going in this site and building.

Thank You! Steffen

Apache Lounge is not sponsored.

Your donations will help to keep this site alive and well, and continuing building binaries.



Differences with mod_header

 
Post new topic   Reply to topic    Apache Forum Index -> Apache



View previous topic :: View next topic  
Author Message
pbhq



Joined: 17 Mar 2013
Posts: 37
Location: Germany

PostPosted: Mon 18 Feb '19 20:29    Post subject: Differences with mod_header Reply with quote

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: 2185
Location: Sun Diego, USA

PostPosted: Tue 19 Feb '19 0:56    Post subject: Reply with quote

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

PostPosted: Tue 19 Feb '19 18:11    Post subject: Reply with quote

Thanks, I saw it.

No, the bug is independent of http/1.1 or http/2.0. That was my first guess ... Wink
Back to top


Post new topic   Reply to topic    Apache Forum Index -> Apache
Page 1 of 1