mirror of
https://github.com/moparisthebest/curl
synced 2024-11-11 12:05:06 -05:00
8f3c3cd08a
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
41 lines
578 B
Plaintext
41 lines
578 B
Plaintext
<testcase>
|
|
<info>
|
|
<keywords>
|
|
GOPHER
|
|
QUERY
|
|
</keywords>
|
|
</info>
|
|
|
|
#
|
|
# Server-side
|
|
<reply>
|
|
<data>
|
|
iSearch results error.host 1
|
|
0Query query succeeded /foo foo.bar.invalid 70
|
|
0Selector /the/search/engine /bar bar.foo.invalid 70
|
|
.
|
|
</data>
|
|
</reply>
|
|
|
|
# Client-side
|
|
<client>
|
|
<server>
|
|
gopher
|
|
</server>
|
|
<name>
|
|
Gopher query
|
|
</name>
|
|
<command>
|
|
"gopher://%HOSTIP:%GOPHERPORT/7/the/search/engine%09query%20succeeded/1202"
|
|
</command>
|
|
</client>
|
|
|
|
#
|
|
# Verify data after the test has been "shot"
|
|
<verify>
|
|
<protocol>
|
|
/the/search/engine query succeeded/1202
|
|
</protocol>
|
|
</verify>
|
|
</testcase>
|