HTTP: What is the preferred Accept-Encoding for "gzip, deflate"?

This question is about the priority order for the media types of the Accept-Encoding HTTP header, when everyone has the same weight , and he was offered this comment on my blog.

Reference Information:

The Accept-Encoding header accepts a comma-separated list of media types that the browser can accept, for example. Gzip, deflate

You can also specify a quality factor to give preference to other media types, for example. in the case of "gzip; q = .8, deflate", rejection is preferable - but not relevant. NB: A type with "q = 0" means "unacceptable."

RFC2616 also indicates that the “most specific link” must first be weighted to determine the type of media. those. "text / html; level = 1" should be used above "text / html" - this also does not apply to the question.

Question:

In the following case, which medium has priority?

Accept-Encoding: gzip,deflate

Both types have an equivalent quality factor of 1, and both types are "acceptable" to the browser, so you can use one of them. I always assumed that the first type introduced should be “preferred,” but there seems to be no concrete example or preference for this particular case in the RFC .

+5
2

- RFC RFC, , .

gzip vs deflate , , deflate, - ( , adler32, crc32 ). , . . , . . gzip - , unix, .

, gzip - , - . , , .

, , gzip. , . , , 5 ASP.NET.

+5

. , ( ).

0

All Articles