diff options
author | Leonardo Taccari <iamleot@gmail.com> | 2018-08-23 23:27:34 +0200 |
---|---|---|
committer | Daniel Stenberg <daniel@haxx.se> | 2018-08-24 08:57:49 +0200 |
commit | 8f3c3cd08a5b252002a4abfb19780850fc51040e (patch) | |
tree | 250835eb90c46584c1ba55bd88d40c4cd7008868 /tests/data | |
parent | 387e85efd08d9a7d184c9fd37cba61110728e511 (diff) | |
download | curl-8f3c3cd08a5b252002a4abfb19780850fc51040e.tar.gz |
gopher: Do not translate `?' to `%09'
Since GOPHER support was added in curl `?' character was automatically
translated to `%09' (`\t').
However, this behaviour does not seems documented in RFC 4266 and for
search selectors it is documented to directly use `%09' in the URL.
Apart that several gopher servers in the current gopherspace have CGI
support where `?' is used as part of the selector and translating it to
`%09' often leads to surprising results.
Closes #2910
Diffstat (limited to 'tests/data')
-rw-r--r-- | tests/data/test1202 | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/tests/data/test1202 b/tests/data/test1202 index 37d270acb..6c91a774c 100644 --- a/tests/data/test1202 +++ b/tests/data/test1202 @@ -26,7 +26,7 @@ gopher Gopher query </name> <command> -"gopher://%HOSTIP:%GOPHERPORT/7/the/search/engine?query%20succeeded/1202" +"gopher://%HOSTIP:%GOPHERPORT/7/the/search/engine%09query%20succeeded/1202" </command> </client> |