diff options
author | Anthony Ramine <[email protected]> | 2015-01-02 16:04:33 +0100 |
---|---|---|
committer | Anthony Ramine <[email protected]> | 2015-01-02 16:04:33 +0100 |
commit | e564cfb82f28fa24ed842ee96e2addf41180700d (patch) | |
tree | 8971d29f338190773cbb1b8c68381b06c0137eab /lib/inets/doc/src/http_uri.xml | |
parent | af87b1c3d4897840d8247589a88d3611106ecedc (diff) | |
download | otp-e564cfb82f28fa24ed842ee96e2addf41180700d.tar.gz otp-e564cfb82f28fa24ed842ee96e2addf41180700d.tar.bz2 otp-e564cfb82f28fa24ed842ee96e2addf41180700d.zip |
Properly parse URI fragments
This fixes a bug in httpc where redirection URIs could lead to bad requests if they
contained fragments.
Diffstat (limited to 'lib/inets/doc/src/http_uri.xml')
-rw-r--r-- | lib/inets/doc/src/http_uri.xml | 11 |
1 files changed, 9 insertions, 2 deletions
diff --git a/lib/inets/doc/src/http_uri.xml b/lib/inets/doc/src/http_uri.xml index e64c375bba..acbd79b201 100644 --- a/lib/inets/doc/src/http_uri.xml +++ b/lib/inets/doc/src/http_uri.xml @@ -63,6 +63,7 @@ host() = string() port() = pos_integer() path() = string() - Representing a file path or directory path query() = string() +fragment() = string() ]]></code> <marker id="scheme_defaults"></marker> @@ -92,13 +93,16 @@ query() = string() <v>URI = uri() </v> <v>Options = [Option] </v> <v>Option = {ipv6_host_with_brackets, boolean()} | - {scheme_defaults, scheme_defaults()}]</v> - <v>Result = {Scheme, UserInfo, Host, Port, Path, Query}</v> + {scheme_defaults, scheme_defaults()} | + {fragment, boolean()}]</v> + <v>Result = {Scheme, UserInfo, Host, Port, Path, Query} | + {Scheme, UserInfo, Host, Port, Path, Query, Fragment}</v> <v>UserInfo = user_info()</v> <v>Host = host()</v> <v>Port = pos_integer()</v> <v>Path = path()</v> <v>Query = query()</v> + <v>Fragment = fragment()</v> <v>Reason = term() </v> </type> <desc> @@ -111,6 +115,9 @@ query() = string() a scheme not found in the scheme defaults) a port number must be provided or else the parsing will fail. </p> + <p>If the fragment option is true, the URI fragment will be returned as + part of the parsing result, otherwise it is completely ignored.</p> + <marker id="encode"></marker> </desc> </func> |