W3C home > Mailing lists > Public > www-forms@w3.org > October 2005

HTTP Response Headers

From: <andyh@collegenet.com>
Date: Fri, 7 Oct 2005 09:17:16 -0700
To: www-forms@w3.org
Message-ID: <OF1885782D.8DAB5822-ON88257093.00575535-88257093.00596F8D@collegenet.com>





Hi,

Does anyone have any ideas as to how we could handle the response headers
from an HTTP request?

The specific use case I have in mind is when using a REST style
architecture I want to POST a new resource to a generic URI:

eg. POST events.xml
<event status="new">...</event>

will cause a new "event" to be created. The expected response from the
server is a status of 201 and a Location header that specifies the URI of
the new resource [1]


formsPlayer has implemented an extension to the submission element to allow
us to set the request headers, but there is nothing for handling the
response, including the specific HTTP status and access to the Location
header.

Of couse one solution/workaround is that the response body contains this
information. But my other use case would involve authorization where the
server challenges with a 401 and the client is expected, in an
xforms-submit-error action, to pick up on the WWW-Authenticate header in
the subsequent response.


Maybe a responseheaders (and requestheaders) attribute on the submission
element that is a reference to an instance?

--
Andy Heydon


[1] HTTP 1.1, RFC2616, Section 9.5
Received on Friday, 7 October 2005 16:17:49 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Saturday, 10 March 2012 06:22:02 GMT