```json
{
    "title": "Symantec Firewall — Problems with Accept-Encoding Headers",
    "url": "https://performancezen.com/2005/03/10/symantec-firewall-problems-with-accept-encoding-headers/",
    "datePublished": "2005-03-10",
    "dateModified": "2005-03-10",
    "language": "en-US",
    "description": "Here is a little tidbit that we discovered while trying to debug an issue at work. One of my colleagues found that the Symantec/Norton Personal Firewall/Internet Security mangles the \"Accept-Encoding\"…",
    "author": "spierzchala",
    "publisher": "Performance Zen"
}
```

# Symantec Firewall — Problems with Accept-Encoding Headers

Here is a little tidbit that we discovered while trying to debug an issue at work. One of my colleagues found that the Symantec/Norton Personal Firewall/Internet Security mangles the "Accept-Encoding" header sent out by any application -- browser, streaming media, etc.
More can be found [here](http://www.wmptalk.com/ftopic8586.html).
This is a serious problem, and has a negative effect on Web performance in general, as one of the key methods for improving bandwidth consumption and user performance is Server-Side Compression of as much content as possible.
What the client wants to send: Accept-Encoding: gzip,deflate\r\n
What is sent: ---------------: ---- -------\r\n
What is the problem? Is this because Symantec can't parse compressed content on the fly?