Plugins:GenericHttpMethod: Difference between revisions
Jump to navigation
Jump to search
| Line 10: | Line 10: | ||
# Confusion about how invalid URLs (for instance, containing non-ASCII characters or whitespace) need to be handled. | # Confusion about how invalid URLs (for instance, containing non-ASCII characters or whitespace) need to be handled. | ||
= Existing Discussions and Documentation = | = Existing Discussions and Documentation = | ||
== Related Documentation == | |||
* [http://www.w3.org/TR/XMLHttpRequest/ XMLHttpRequest] (demonstrates that browsers already support the required functionality and could be used to define certain behaviors, such as how request headers are defaulted and combined) | |||
= API Requirements = | = API Requirements = | ||
= Current Proposal = | = Current Proposal = | ||
Revision as of 15:39, 19 August 2009
Status
Under Consideration
Problem Summary
- The plugin API only supports GET and POST. It would be desirable to support other methods defined in RFC 2616, such as DELETE, OPTIONS, and PUT, and also extension methods such as PROPFIND (WebDAV) or PATCH.
- HTTP request headers can only be set for POST (see NPN_PostURLNotify), but not for GET (NPN_GetURLNotify). This makes it hard to access content-negotiated resources.
- There is unsufficient control over handling HTTP redirects (need details).
- Confusion about how invalid URLs (for instance, containing non-ASCII characters or whitespace) need to be handled.
Existing Discussions and Documentation
Related Documentation
- XMLHttpRequest (demonstrates that browsers already support the required functionality and could be used to define certain behaviors, such as how request headers are defaulted and combined)