Re: ERROR verb

[Ryan Tomayko <rtomayko@xxxxxxxxx>]

On Sat, 19 Jun 2004 21:35:42 +0200, Julian Reschke 
> Ryan Tomayko wrote:
> > I would like to add to Bill's remarks and suggest that discussion
> > around ERR thus far has assumed that a single resource maps to a
> > single representation. [snip]
> That's why I was suggesting to include the Entity Tag that was sent with
> the broken content (note that if strong entity tags are present, they
> MUST be distinct for different variants of the resource).

Ahh. Not sure how I missed that. Sorry.

Ryan

On Sat, 19 Jun 2004 21:35:42 +0200, Julian Reschke
<julian.reschke@xxxxxx> wrote:
> 
> Ryan Tomayko wrote:
> 
> > I would like to add to Bill's remarks and suggest that discussion
> > around ERR thus far has assumed that a single resource maps to a
> > single representation. The Accept, Accept-Charset, Accept-Language,
> > and User-Agent request headers can all be used by the server to
> > respond with varying representations of the resource identified by the
> > requested URI. The URI alone may not be sufficient to notify the
> > server of the problem. For instance, if the application/atom+xml,
> > Shift_JIS, ja version of http://bla.com/feed is invalid, how does ERR
> > specify that? It might be possible to send the Content-Type and
> > Content-Language header values as request headers with ERR but now
> > we're really redifining the semantics of those headers within this
> > context.
> 
> That's why I was suggesting to include the Entity Tag that was sent with
> the broken content (note that if strong entity tags are present, they
> MUST be distinct for different variants of the resource).
> 
> 
> 
> Best regards, Julian
> 
> --
> <green/>bytes GmbH -- http://www.greenbytes.de -- tel:+492512807760
>