Re: Feedback on content transformation guidelines (LC-2066 & al.)

> We could tighten the wording not to say that a 200 
> response can be treated as a 406 response where we 
> mean to say "as a response to a request with a
> browser that is not supported". The browser's 
> (non-)identification is likely to be based on the 
> User-Agent and not on the accept HTTP headers.

Or use a 403-Forbidden response, which contrarily to 
what its name indicates, seems to be a generic rejection 
form of a request. The 403 response can be accompanied
with an explanatory text.


E.Casais


      

Received on Monday, 7 December 2009 14:50:25 UTC