do a POST with NTLM and add two custom headers

 test237 test238 test239 test243 test245 test246 test247 test248 test249   \

 test250 test251 test252 test253 test254 test255 test521 test522 test523   \

 test256 test257 test258 test259 test260 test261 test262 test263 test264   \

 test265 test266

 test265 test266 test267

<info>

<keywords>

HTTP

HTTP POST

HTTP NTLM auth

</keywords>

</info>

# Server-side

<reply>

# no <data> in this test since we have NTLM from the start

# This is supposed to be returned when the server gets a first

# Authorization: NTLM line passed-in from the client

<data1001>

HTTP/1.1 401 Now gimme that second request of crap

Server: Microsoft-IIS/5.0

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

Content-Length: 34

WWW-Authenticate: NTLM TlRMTVNTUAACAAAAAgACADAAAAAGgoEAc51AYVDgyNcAAAAAAAAAAG4AbgAyAAAAQ0MCAAQAQwBDAAEAEgBFAEwASQBTAEEAQgBFAFQASAAEABgAYwBjAC4AaQBjAGUAZABlAHYALgBuAHUAAwAsAGUAbABpAHMAYQBiAGUAdABoAC4AYwBjAC4AaQBjAGUAZABlAHYALgBuAHUAAAAAAA==

This is not the real page either!

</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 server land swsclose

Server: Microsoft-IIS/5.0

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

Finally, this is the real page!

</data1002>

<datacheck>

HTTP/1.1 401 Now gimme that second request of crap

Server: Microsoft-IIS/5.0

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

Content-Length: 34

WWW-Authenticate: NTLM TlRMTVNTUAACAAAAAgACADAAAAAGgoEAc51AYVDgyNcAAAAAAAAAAG4AbgAyAAAAQ0MCAAQAQwBDAAEAEgBFAEwASQBTAEEAQgBFAFQASAAEABgAYwBjAC4AaQBjAGUAZABlAHYALgBuAHUAAwAsAGUAbABpAHMAYQBiAGUAdABoAC4AYwBjAC4AaQBjAGUAZABlAHYALgBuAHUAAAAAAA==

HTTP/1.1 200 Things are fine in server land swsclose

Server: Microsoft-IIS/5.0

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

Finally, this is the real page!

</datacheck>

</reply>

# Client-side

<client>

<features>

NTLM

</features>

<server>

http

</server>

 <name>

HTTP POST with NTLM authorization and added custom headers

 </name>

 <command>

http://%HOSTIP:%HTTPPORT/267 -u testuser:testpass --ntlm -d "data" -H "Header1: yes" -H "Header2: no"

</command>

</client>

# Verify data after the test has been "shot"

<verify>

<strip>

^User-Agent:.*

</strip>

<protocol nonewline=yes>

POST /267 HTTP/1.1

Authorization: NTLM TlRMTVNTUAABAAAAAgIAAAAAAAAgAAAAAAAAACAAAAA=

User-Agent: curl/7.10.6-pre1 (i686-pc-linux-gnu) libcurl/7.10.6-pre1 OpenSSL/0.9.7a ipv6 zlib/1.1.3

Host: 127.0.0.1:%HTTPPORT

Accept: */*

Header1: yes

Header2: no

Content-Length: 0

Content-Type: application/x-www-form-urlencoded

POST /267 HTTP/1.1

Authorization: NTLM TlRMTVNTUAADAAAAGAAYAEgAAAAYABgAYAAAAAAAAABAAAAACAAIAEAAAAAAAAAASAAAAAAAAAB4AAAAAYIAAHRlc3R1c2VyWmRDApEJkUyGOPS3DjvASModEeW/N/FBqYVyF4y6/y/7F6qmEQ7lXjXFF3tH1145

User-Agent: curl/7.10.6-pre1 (i686-pc-linux-gnu) libcurl/7.10.6-pre1 OpenSSL/0.9.7a ipv6 zlib/1.1.3

Host: 127.0.0.1:%HTTPPORT

Accept: */*

Header1: yes

Header2: no

Content-Length: 4

Content-Type: application/x-www-form-urlencoded

data

</protocol>

</verify>