Jonas Sicking wrote:
No. Look, if you don't want to have to take on the extra work of
fully supporting HTTP (for what is, admittedly, currently a fringe
case), fine, don't. Just please don't ask that we tell those who are
willing to do so, that they can't.
Given that none of the current browsers support this today, I'm not sure
who we would help by saying that this is non-conformant behavior.
The suggestion was *not* to say anything about it, and just to rely on
the normative spec for it, which is RFC2616 now and will be RFC2616bis
in the future.
BR, Julian
