1
0
mirror of https://github.com/moparisthebest/curl synced 2024-11-04 16:45:06 -05:00
curl/tests/data/test287
Daniel Stenberg abdbd3100f - Michael Wallner reported that when doing a CONNECT with a custom User-Agent
header, you got _two_ User-Agent headers in the CONNECT request...! Added
  test case 287 to verify the fix.
2007-01-29 09:26:36 +00:00

46 lines
811 B
Plaintext

<testcase>
# Server-side
<reply>
# this is returned first since we get no proxy-auth
<data nocheck="1">
HTTP/1.1 405 Method Not Allowed swsclose
And you should ignore this data.
</data>
</reply>
# Client-side
<client>
<server>
http
</server>
<name>
HTTP proxy CONNECT with custom User-Agent header
</name>
<command>
http://test.remote.server.com:287/path/287 -H "User-Agent: looser/2007" --proxy http://%HOSTIP:%HTTPPORT --proxytunnel
</command>
</client>
# Verify data after the test has been "shot"
<verify>
<protocol>
CONNECT test.remote.server.com:287 HTTP/1.0
Host: test.remote.server.com:287
Proxy-Connection: Keep-Alive
User-Agent: looser/2007
</protocol>
# CURLE_RECV_ERROR
<errorcode>
56
</errorcode>
<stdout>
HTTP/1.1 405 Method Not Allowed swsclose
</stdout>
</verify>
</testcase>