RE: Quick feedback on draft-nottingham-web-proxy-desc-00

>> Rightfully. This is what RFC 7230 already requires.

Why rightfully, though? The example given has merit, and could make the difference between a functional user experience, and not.

Ideally the content server would be providing a response that was suitable for the delivery context, in which case no-transform should indeed be ignored, but that's not always the case in practice. Hence the point about allowing the user to choose.

Cheers
Kevin

Received on Thursday, 2 October 2014 16:20:27 UTC