946
edits
Labs/Weave/Identity/Account Manager/Spec/Latest: Difference between revisions
Labs/Weave/Identity/Account Manager/Spec/Latest (view source)
Revision as of 23:50, 8 April 2010
, 8 April 2010→Method Descriptions
| Line 112: | Line 112: | ||
Each <profile name> element may contain any number of these method descriptions. Each method description must contain these properties: | Each <profile name> element may contain any number of these method descriptions. Each method description must contain these properties: | ||
method: One of the HTTP methods, e.g. GET or POST | <tt>method</tt>: One of the HTTP methods, e.g. GET or POST | ||
path: An absolute path, which will be combined with the scheme and net-location provided in the domain attribute of the document to produce a URL. The path may contain the "?", "=", and "&" characters; it must not contain the "#" character, and if it does, the "#" character and all characters after it MUST be removed by the user-agent. | <tt>path</tt>: An absolute path, which will be combined with the scheme and net-location provided in the domain attribute of the document to produce a URL. The path may contain the "<tt>?</tt>", "<tt>=</tt>", and "<tt>&</tt>" characters; it must not contain the "<tt>#</tt>" character, and if it does, the "<tt>#</tt>" character and all characters after it MUST be removed by the user-agent. | ||
params: A dictionary of name-value pairs. The names that are legal here are defined by each method description; the value of each pair defines the name that will be used to submit that value. For example, in the | <tt>params</tt>: A dictionary of name-value pairs. The names that are legal here are defined by each method description; the value of each pair defines the name that will be used to submit that value. For example, in the <tt>connect</tt> method description, a dictionary entry of <tt>"username":"un"</tt> indicates that the username associated with the connection will be submitted as the "<tt>un</tt>" parameter. | ||
The meaning of each method is determined by each profile. For the Username-Password Form Profile, see section 5.1 below. | The meaning of each method is determined by each profile. For the Username-Password Form Profile, see section 5.1 below. | ||