~?~

~?~

~?~

W3C 12 January 2017 This version: https://www.w3.org/TR/2017/REC-webmention-20170112/ Latest published version: https://www.w3.org/TR/webmention/ Latest editor's draft: https://webmention.net/draft/ Test suite: https://webmention.rocks/ Implementation report: https://webmention.net/implementation-reports/ Previous version: https://www.w3.org/TR/2016/PR-webmention-20161101/ Editor: Aaron Parecki Repository: Github Issues Commits Please check the errata for any errors or issues reported since publication. The English version of this specification is the only normative version. Non-normative translations may also be available. Copyright © 2017 W3C ® ( MIT , ERCIM , Keio , Beihang ). W3C liability , trademark and permissive document license rules apply. Abstract Webmention is a simple way to notify any URL when you mention it on your site. From ...

~?~

previous next contents elements attributes index 17 Forms Contents Introduction to forms Controls Control types The FORM element The INPUT element Control types created with INPUT Examples of forms containing INPUT controls The BUTTON element The SELECT , OPTGROUP , and OPTION elements Pre-selected options The TEXTAREA element The ISINDEX element Labels The LABEL element Adding structure to forms: the FIELDSET and LEGEND elements Giving focus to an element Tabbing navigation Access keys Disabled and read-only controls Disabled controls Read-only controls Form submission Form submission method Successful controls Processing form data Step one: Identify the successful controls Step two: Build a form data set Step three: Encode the form data set Step four: Submit the encoded form data set Form content types application/x-www-for...

part of Hypertext Transfer Protocol -- HTTP/1.1 RFC 2616 Fielding, et al. 10 Each Status-Code is described below, including a description of which method(s) it can follow and any metainformation required in the response. 10.1 This class of status code indicates a provisional response, consisting only of the Status-Line and optional headers, and is terminated by an empty line. There are no required headers for this class of status code. Since HTTP/1.0 did not define any 1xx status codes, servers MUST NOT send a 1xx response to an HTTP/1.0 client except under experimental conditions. A client MUST be prepared to accept one or more 1xx status responses prior to a regular response, even if the client does not expect a 100 (Continue) status message. Unexpected 1xx status responses MAY be ignored by a user agent. Proxies MUST forward 1xx respons...

part of Hypertext Transfer Protocol -- HTTP/1.1 RFC 2616 Fielding, et al. 10 Status Code Definitions Each Status-Code is described below, including a description of which method(s) it can follow and any metainformation required in the response. 10.1 Informational 1xx ...