Re: ERROR verb (was: Re: well-formedness error)

[Henry Story <henry.story@xxxxxxxxxxx>]

:-) 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





On 19 Jun 2004, at 12:28, Asbjørn Ulsberg wrote:

> On Sat, 19 Jun 2004 12:15:53 +0200, Henry Story 
> <henry.story@xxxxxxxxxxx> wrote:
>
> > Could one not generalize and create an ERROR header in addition to 
> > GET, POST
>
> I think this proposal is just millimeters from being genuious. No, as 
> a matter of fact, I think it's genious. Those with more control over 
> their web servers, with scripting capabilities and such, will be able 
> to catch those ERROR requests neatly. Those with statically served 
> pages will get the ERROR requests logged to the server logs.
>
> If everyone is aware of the ERROR verb, it will be easy to track the 
> error down to the ill-formed entry. Does anyone oppose this method? I 
> think it's very RESTful and elegant. If no one else creates it, I'll 
> put up a PaceErrorVerb on the Wiki.
>
> --
> Asbjørn Ulsberg         -=|=-        asbjornu@xxxxxxxxxxx
> «He's a loathsome offensive brute, yet I can't look away»