-
Notifications
You must be signed in to change notification settings - Fork 1.7k
Description
Hi there,
I have appended the same comments below on the following issue "ModSecurity 2.7.5 for Nginx 1.4.2 duplicate charset headers".
In response, I was told that there was an update on the way the header is set and that it was fixed under the development tree.
I have updated my MODSEC with the Branch Master code and I still see the same issue.
Please see below my original comments .... any help would be much appreciated.
Is there a way to prevent MODSEC from adding the second charset-header at all (assuming this is expected behaviour)?
I am running version 2.7.7 on NGINX version 1.4.4 (Ubuntu 12.04 LTS) and I can not find a way to toggle this on / off .... not even sure if this is even possible (sorry.. I am pretty new to modsec).
At the moment I have an issue where with modsecurity enabled we appear to be seeing duplicate charset attributes... for example, Content-Type: text/xml; Charset=UTF-8; charset=UTF-8;.... browsers will ignore the duplicate "Charset=UTF-8; charset=UTF-8"; but this is breaking one of my applications (we think that possibly MSXML is choking on it (when it retrieves such content using a document() call)).. just doesn't like that double charset.... the page throws the following error: "....System does not support the specified encoding......"
Thanks.