Re: Re[2]: HTTP :unsupported content-encoding of '' found

2016-11-19 Thread Andreas Veithen
According to the HTTP/1.1 specification the Content-Encoding header must have the following form: Content-Encoding = "Content-Encoding" ":" 1#content-coding I.e. an empty value is not allowed, so this is a server side problem. Andreas On Nov 19, 2016 4:30 PM, "Sterpu Victor"

Re[2]: HTTP :unsupported content-encoding of '' found

2016-11-19 Thread Sterpu Victor
Yes, I traced everything with fiddler. I can now see that "Content-Encoding: " is not defined. If this is the reason can I safely ignore this error? This is the raw header: HTTP/1.1 200 OK X-Backside-Transport: OK OK Connection: Keep-Alive Transfer-Encoding: chunked Date: Sat, 19 Nov 2016