W3C home > Mailing lists > Public > ietf-http-wg@w3.org > April to June 2004

Re: Proposal for an HTTP ERR method

From: Justin Chapweske <justin@chapweske.com>
Date: Wed, 23 Jun 2004 11:47:25 -0500
To: Henry Story <henry.story@bblfish.net>
Cc: ietf-http-wg@w3.org, Atom Syntax <atom-syntax@imc.org>, Alex Rousskov <rousskov@measurement-factory.com>
Message-Id: <1088009244.27193.94.camel@bog>

Why introduce a new unnecessary method when you could simply issue a
POST to some bug-reporting URI associated with the server?

If you're going to specify anything, submit a proposal to advertise
feedback URIs using a RESTful approach, perhaps in HTTP response headers
such as Link, or within the (x)html itself as a <link> tag.

> Fixing the problem will most probably require some human intervention.
> But if you have just downloaded some broken XML and still have an open 
> connection to the server, why not just send an ERR at that moment to 
> the server. Then it can be clearly logged, and it is also clear what 
> the problem is about.

-- 
Justin Chapweske - Founder, Onion Networks
http://onionnetworks.com/
651-340-8787
 
Transfer large files 10x faster than FTP with Onion Networks' WAN
Transport(tm).  http://onionnetworks.com/products_wantransport.php
Received on Wednesday, 23 June 2004 12:50:14 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 27 April 2012 06:49:31 GMT