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
This commit is contained in:
Leonardo Taccari 2018-08-23 23:27:34 +02:00 committed by Daniel Stenberg
parent 387e85efd0
commit 8f3c3cd08a
No known key found for this signature in database
GPG key ID: 5CC908FDB71E12C2
2 changed files with 1 additions and 8 deletions

View file

@ -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>