- From: Cameron Jones <cmhjones@gmail.com>
- Date: Thu, 17 Apr 2014 14:42:29 +0100
- To: "public-html@w3.org LIST" <public-html@w3.org>
- Message-ID: <CALGrgevt4d6bS7mu9HuGEShXUB7GA2H+qmF09z5C1cKRrYav2w@mail.gmail.com>
Dear all, I am about to submit an email to public-html-admin requesting the publication of an extension specification for Form HTTP Extensions. Prior to this and minting a FPWD snapshot i would like to initiate this thread for any further technical discussion over the specification. The current editor's draft resides here: http://cameronjones.github.io/form-http-extensions/index.html The extension specification resolves the previously tracked "ISSUE-195: Enhance http request generation from forms": http://www.w3.org/html/wg/tracker/issues/195 In summary, the extension amount to the following changes: * Remove restrictions on form HTTP methods to allow for PUT and DELETE methods, in addition to HTTP extension-methods for private\experimental use under CORS restrictions. * Introduce @payload submission attribute on form controls allowing targeting URL queries, HTTP headers and message data from user input or hidden fields. * Extends the use of named form control fields to include "_username_" and "_password_" for integration with User Agent HTTP Authentication, akin to XHR open() method arguments. * Additional "_logout_" named form control field for initiating clearing of User Agent HTTP Authentication Cache defined by RFC2617 "protection space". The following is a list of additional references with further discussion and/or information: http://lists.whatwg.org/htdig.cgi/whatwg-whatwg.org/2013-February/208357.html http://lists.w3.org/Archives/Public/public-html/2013Feb/0227.html Feedback is most welcome! Thanks, Cameron Jones
Received on Thursday, 17 April 2014 13:42:56 UTC