88
edits
Plugins:GenericHttpMethod: Difference between revisions
Jump to navigation
Jump to search
→Problem Summary
| Line 9: | Line 9: | ||
# There is insufficient control over handling HTTP redirects. If a redirect is followed automatically, the caller should be able to find out the type of redirect (temporary or permanent) and the new URI. If a redirect was not followed, it should have access to status code and Location header. And finally it should be able to select whether redirects are followed or not. (Note that currently this isn't covered by XmlHttpRequest either, but is a known [http://www.w3.org/TR/XMLHttpRequest/#notcovered to-do]) | # There is insufficient control over handling HTTP redirects. If a redirect is followed automatically, the caller should be able to find out the type of redirect (temporary or permanent) and the new URI. If a redirect was not followed, it should have access to status code and Location header. And finally it should be able to select whether redirects are followed or not. (Note that currently this isn't covered by XmlHttpRequest either, but is a known [http://www.w3.org/TR/XMLHttpRequest/#notcovered to-do]) | ||
# 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. | ||
Future extensions we should plan for: | |||
# Access to provisional 1xx responses. | |||
= Existing Discussions and Documentation = | = Existing Discussions and Documentation = | ||