fre 2012-04-27 klockan 13:50 -0700 skrev Andrew Scherkus: > As far as Chromium is concerned we use ETag headers as a strong > validator to determine when we should cache content and when to > invalidate and re-fetch content should the ETag change. Since ETag and > ranges aren't technically part of the HTTP/1.0 spec we ignore them > skip caching the content.
You should generally not ignore HTTP/1.1 features seen within HTTP/1.0. The exceptions is those marked as MUST NOT send in response to HTTP/1.0 in the HTTP/1.1 spec. Regards Henrik
