added test 1021 to verify my fix for bug report #1879375

 test1010 test1011 test1012 test542 test543 test536 test1008 test1009	   \

 test2000 test2001 test2002 test2003 test35 test544 test545 test2004	   \

 test546 test1013 test1014 test1015 test547 test548 test549 test550	   \

 test551 test552 test1016 test1017 test1018 test1019 test1020 test553

 test551 test552 test1016 test1017 test1018 test1019 test1020 test553      \

 test1021

filecheck:

	@mkdir test-place; \

<testcase>

<info>

<keywords>

HTTP

HTTP GET

HTTP proxy

HTTP proxy NTLM auth

CONNECT

</keywords>

</info>

# Server-side

<reply>

<data>

HTTP/1.1 407 Authorization Required to proxy me my dear swsclose

Proxy-Authenticate: NTLM

Content-Length: 21

Connection: close

data to discard

</data>

# this is returned first since we get no proxy-auth

<data1001>

HTTP/1.1 407 Authorization Required to proxy me my dear

Proxy-Authenticate: NTLM TlRMTVNTUAACAAAAAgACADAAAAAGgoEAc51AYVDgyNcAAAAAAAAAAG4AbgAyAAAAQ0MCAAQAQwBDAAEAEgBFAEwASQBTAEEAQgBFAFQASAAEABgAYwBjAC4AaQBjAGUAZABlAHYALgBuAHUAAwAsAGUAbABpAHMAYQBiAGUAdABoAC4AYwBjAC4AaQBjAGUAZABlAHYALgBuAHUAAAAAAA==

Content-Length: 28

And you should ignore this data.

</data1001>

# This is supposed to be returned when the server gets the second

# Authorization: NTLM line passed-in from the client

<data1002>

HTTP/1.1 200 Things are fine in proxy land

Server: Microsoft-IIS/5.0

Content-Type: text/html; charset=iso-8859-1

</data1002>

# this is returned when we get a GET!

<data2>

HTTP/1.1 200 OK

Date: Thu, 09 Nov 2010 14:49:00 GMT

Content-Length: 7

Connection: close

Content-Type: text/html

Funny-head: yesyes

daniel

</data2>

# then this is returned when we get proxy-auth

<data1000>

HTTP/1.1 200 OK swsbounce

Server: no

Nice proxy auth sir!

</data1000>

<datacheck>

HTTP/1.1 407 Authorization Required to proxy me my dear swsclose

Proxy-Authenticate: NTLM

Content-Length: 21

Connection: close

HTTP/1.1 407 Authorization Required to proxy me my dear

Proxy-Authenticate: NTLM TlRMTVNTUAACAAAAAgACADAAAAAGgoEAc51AYVDgyNcAAAAAAAAAAG4AbgAyAAAAQ0MCAAQAQwBDAAEAEgBFAEwASQBTAEEAQgBFAFQASAAEABgAYwBjAC4AaQBjAGUAZABlAHYALgBuAHUAAwAsAGUAbABpAHMAYQBiAGUAdABoAC4AYwBjAC4AaQBjAGUAZABlAHYALgBuAHUAAAAAAA==

Content-Length: 28

HTTP/1.1 200 Things are fine in proxy land

Server: Microsoft-IIS/5.0

Content-Type: text/html; charset=iso-8859-1

HTTP/1.1 200 OK

Date: Thu, 09 Nov 2010 14:49:00 GMT

Content-Length: 7

Connection: close

Content-Type: text/html

Funny-head: yesyes

daniel

</datacheck>

</reply>

# Client-side

<client>

<server>

http

</server>

<features>

NTLM

</features>

 <name>

HTTP proxy CONNECT with any proxyauth and proxy offers NTLM and close

 </name>

 <command>

http://test.remote.server.com:1021/path/10210002 --proxy http://%HOSTIP:%HTTPPORT --proxy-user silly:person --proxy-anyauth --proxytunnel

</command>

</client>

# Verify data after the test has been "shot"

<verify>

<strip>

^User-Agent: curl/.*

</strip>

# We strip off a large chunk of the type-2 NTLM message since it depends on

# the local host name and thus differs on different machines!

<strippart>

s/^(Proxy-Authorization: NTLM TlRMTVNTUAADAAAAGAAYAEAAAAAYABgAWAAAAAAAAABwAAAABQAFAHAAAAA).*/$1/

</strippart>

<protocol>

CONNECT test.remote.server.com:1021 HTTP/1.0

Host: test.remote.server.com:1021

Proxy-Connection: Keep-Alive

CONNECT test.remote.server.com:1021 HTTP/1.0

Host: test.remote.server.com:1021

Proxy-Authorization: NTLM TlRMTVNTUAABAAAABoIIAAAAAAAAAAAAAAAAAAAAAAA=

Proxy-Connection: Keep-Alive

CONNECT test.remote.server.com:1021 HTTP/1.0

Host: test.remote.server.com:1021

Proxy-Authorization: NTLM TlRMTVNTUAADAAAAGAAYAEAAAAAYABgAWAAAAAAAAABwAAAABQAFAHAAAAA

Proxy-Connection: Keep-Alive

GET /path/10210002 HTTP/1.1

User-Agent: curl/7.12.3-CVS (i686-pc-linux-gnu) libcurl/7.12.3-CVS OpenSSL/0.9.6b zlib/1.1.4

Host: test.remote.server.com:1021

Accept: */*

</protocol>

</verify>

</testcase>