Hi Ian, On Tue, Jan 17, 2012 at 09:32:03PM +0000, Ian Hickson wrote: > On Sun, 15 Jan 2012, Willy Tarreau wrote: > > > > For instance, if I get a file advertised like this : > > > > Content-type: text/plain; charset=us-ascii > > > > then it will not be interpreted as text/plain > > What makes you think that? As far as I can tell, the algorithm given in > the spec requires that such a file be treated as text/plain.
You're right, as I said in the second mail following this one, I found what I misread in the algorithm. In short, I thought we'd jump to the content analysis if the header did not match these exact forms, which is not the case, I conflated official-type and sniffed-type in the text if my memory serves me right. Regards, Willy _______________________________________________ websec mailing list [email protected] https://www.ietf.org/mailman/listinfo/websec
