On Tue, Jan 20, 2015 at 11:09 AM, Curry, Alan <pacurry@xxxxxxxxxxxxx> wrote: > I'm slightly worried based on the bug report referenced above that 2.4 > may not have a solution to this problem. But it really shouldn't be that > way. Sending any response without a Content-Type is a violation of the > SHOULD in RFC2616 7.2.1. As such it shouldn't be happening without a > good reason. RFC7231 obsoletes 2616 and drops this recommendation. The general idea is that instead of defaulting, omit it so browsers can sniff a content-type when they absolutely have to (and not have to second-guess other content-types by sniffing). I think the idea of a default content-type is considered harmful for the server/browser ecosystem. (The author of RFC2616, RFC7321, and the patch no-op'ing DefaultType are all the same person) -- Eric Covener covener@xxxxxxxxx --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
|