On 8/3/08, Felix Meschberger <[EMAIL PROTECTED]> wrote: > Hi, > > Tobias Bocanegra schrieb: > > > > > > Not necessarily. The HTTP spec mentions headers explicitly for content > > > negotiation > > > > (http://www.w3.org/Protocols/rfc2616/rfc2616-sec12.html) > > > and there might be enough cases where a resource (!) happens to have a > name > > > ending with .html without implying that it is actually HTML. The server > > > selects the representation that is being sent and the server determines > how > > > to value headers or not. > > > > > content negotiation is certainly an interesting capability, but IMO > > poses a lot of problems. for example, i don't want another > > representation of a document (for the same url) just because my > > browser locale is different. if the urls are not stable, the documents > > can't be cached, which is bad. > > > > Well, the URLs are stable in that they always select the same resource. But > the representation differs and hence the resulting representation is not > cacheable. ...which is not favorable. at least not for GET requests.
> HTTP provides various ways for the response to be selectively cache in the > form of the Cache-Control and Vary headers. > > Regards > Felix >
