There is an unsaved comment in progress. You will lose your changes if you continue. Are you sure you want to reopen the work item?
Wrong EncodingName in NullCompressor
I found a bug which took me a long long time to find. It seems that the NullCompressor set the EncodingName property to "utf-8". This in turn results in that the Content-Encoding response header is set to "utf-8" for clients that does not
This is wrong.The correct encoding when no compression is applied should be: "identity".
"utf-8" seems to be working in most browsers but I found that on some phones and only on the swedish cell carrier "Telia" files served with combress did not work. After alot of poking I found that the gateway of "Telia" responded
with that UTF-8 was not a valid encoding and did not server the file. This was later traced to combres.
Could you please fix this?