Re: ERROR verb

[Julian Reschke <julian.reschke@xxxxxx>]

Henry Story wrote:
> :-) I like being called a genius. Keep up the good work! +2
>
> Some other headers that might have to be sent would be information about 
> the original header.
> eg:
>
> ERROR /blog/blog.rss HTTP/1.1
> Host: bblfish.net
> Error-Message: RSS is badly formatted
> Error-Date: Saturday 19 June 2004
> Connection: keep-alive
> Referer: http://bblfish.net/blog/
> User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X; en-us) 
> AppleWebKit/125.2 (KHTML, like Gecko) Safari/125.8
> Accept: */*
> Accept-Encoding: gzip, deflate;q=1.0, identity;q=0.5, *;q=0
> Accept-Language: en-us, ja;q=0.62, de-de;q=0.93, de;q=0.90, 
> fr-fr;q=0.86, fr;q=0.83, nl-nl;q=0.79, nl;q=0.76, it-it;q=0.72, 
> it;q=0.69, ja-jp;q=0.66, en;q=0.97, es-es;q=0.59, es;q=0.55, 
> da-dk;q=0.52, da;q=0.48, fi-fi;q=0.45, fi;q=0.41, ko-kr;q=0.38

- Don't put plain english into the response header. Consider using a URI 
instead (that URI might identify a particular constraint that has been 
violated)

- To identify the response entity that caused the error, send it's 
entitiy tag

Best regards, Julian

--
<green/>bytes GmbH -- http://www.greenbytes.de -- tel:+492512807760