W3C home > Mailing lists > Public > ietf-http-wg@w3.org > October to December 2016

Re: ID for Immutable

From: Kari Hurtta <hurtta-ietf@elmme-mailer.org>
Date: Sat, 29 Oct 2016 08:49:29 +0300 (EEST)
Message-Id: <201610290549.u9T5nThC023236@shell.siilo.fmi.fi>
To: Patrick McManus <pmcmanus@mozilla.com>
CC: Kari Hurtta <hurtta-ietf@elmme-mailer.org>, HTTP working group mailing list <ietf-http-wg@w3.org>
Patrick McManus <pmcmanus@mozilla.com>: (Fri Oct 28 18:01:12 2016)
> Hey Kari, In my distaste for response header hashes, I did hastily neglect
> to mention that one of my implementation corner cases was to ignore
> immutable in cases of weakly framed content.. we define weakly framed as
> responses terminated by EOF or with Content-Lengths that don't match, or
> chunked encodings without a 0 chunk at the end. Experience has shown that
> we have to accept these responses for reasons of interop - but discretion
> says to ignore immutable on them as they may be indications of corruption.
> The ID should mention this - I'll put in -01. Thanks.
> 
> worth noting here that the refresh conditional-request path that immutable
> impacts has never helped much with the corruption case.. it conditionally
> verifies etags or l-m, but generally the corruption is in the message body
> - most often truncation. so a 304 reply confirms to the client to keep
> using the corrupted content anyhow.. 

So on these case that heuristic that ignore immutable for
"weakly framed content" does not help either. 304 reply
still confirms to the client to keep using the corrupted content.

My suggestion using immutable=<property from bydy> for ignnoring
immutable was making that more explicit than heuristic. But
that does change  is that ignoring usefull or not.

/ Kari Hurtta
Received on Saturday, 29 October 2016 05:50:04 UTC

This archive was generated by hypermail 2.3.1 : Saturday, 29 October 2016 05:50:05 UTC