Proposed Accept-Encoding header filter change.

[whenever]

(Dec. 29, 2010 05:21 PM)JJoe Wrote:  The empty header could be sent when the User-Agent wasn't sending an empty header. Doesn't seem like the thing to do?

Just got your point. Your fix is reasonable.

(Dec. 29, 2010 05:21 PM)JJoe Wrote:  However, Opera still sends x-gzip and I found an app that added support years after its creators considered x-gzip to be deprecated. Why?

Opera users suffer pain for its sending x-gzip.

I don't know why they stick with x-gzip but rare cases shouldn't be handled by a filter's default behaving. Exception list is for that purpose.

(Dec. 29, 2010 05:21 PM)JJoe Wrote:  Am also considering forcing gzip only when deflate and gzip are present and or throwing a flag for deflate compressed files.

Doesn't put gzip first fix the issue?

(Dec. 29, 2010 05:21 PM)JJoe Wrote:  The new filter allows the user to do as they wish.
Question is what should the default be?

I think the default should be behave as what most popular browsers like IE/FF do, because most servers/apps will try to keep compatibility with them too.