Add tests of auth retries (24c43e9d) · Commits · CYBER - Cyber Security / TS 103 523 MSP / TLMSP / TLMSP curl

tests/data/Makefile.am

+4 −1

Original line number	Diff line number	Diff line
		@@ -95,7 +95,10 @@ test1400 test1401 test1402 test1403 test1404 test1405 test1406 test1407 \
		test1408 test1409 test1410 \
		test2000 test2001 test2002 test2003 test2004 test2005 test2006 test2007 \
		test2008 test2009 test2010 test2011 test2012 test2013 test2014 test2015 \
		test2016 test2017 test2018 test2019 test2020 test2021 test2022
		test2016 test2017 test2018 test2019 test2020 test2021 test2022 \
		test2023 test2024 test2025 \
		test2026 test2027 test2028 \
		test2029 test2030 test2031

		EXTRA_DIST = $(TESTCASES) DISABLED

tests/data/test2023

0 → 100644

+162 −0

Original line number	Diff line number	Diff line
		<testcase>
		<info>
		<keywords>
		HTTP
		HTTP GET
		HTTP Basic auth
		</keywords>
		</info>
		# Server-side
		<reply>

		<!-- First request has Basic auth, wrong password -->
		<data100>
		HTTP/1.1 401 Sorry wrong password
		Server: Microsoft-IIS/5.0
		Content-Type: text/html; charset=iso-8859-1
		Content-Length: 29
		WWW-Authenticate: Basic realm="testrealm"

		This is a bad password page!
		</data100>

		<!-- Second request has Basic auth, right password -->
		<data200>
		HTTP/1.1 200 Things are fine in server land
		Server: Microsoft-IIS/5.0
		Content-Type: text/html; charset=iso-8859-1
		Content-Length: 32

		Finally, this is the real page!
		</data200>

		<!-- Third request has Basic auth, wrong password -->
		<data300>
		HTTP/1.1 401 Sorry wrong password (2)
		Server: Microsoft-IIS/5.0
		Content-Type: text/html; charset=iso-8859-1
		Content-Length: 29
		WWW-Authenticate: Basic realm="testrealm"

		This is a bad password page!
		</data300>

		<!-- Fourth request has Basic auth, wrong password -->
		<data400>
		HTTP/1.1 401 Sorry wrong password (3)
		Server: Microsoft-IIS/5.0
		Content-Type: text/html; charset=iso-8859-1
		Content-Length: 29
		WWW-Authenticate: Basic realm="testrealm"

		This is a bad password page!
		</data400>

		<!-- Fifth request has Basic auth, right password -->
		<data500>
		HTTP/1.1 200 Things are fine in server land (2)
		Server: Microsoft-IIS/5.0
		Content-Type: text/html; charset=iso-8859-1
		Content-Length: 32

		Finally, this is the real page!
		</data500>

		<datacheck>
		HTTP/1.1 401 Sorry wrong password
		Server: Microsoft-IIS/5.0
		Content-Type: text/html; charset=iso-8859-1
		Content-Length: 29
		WWW-Authenticate: Basic realm="testrealm"

		This is a bad password page!
		HTTP/1.1 200 Things are fine in server land
		Server: Microsoft-IIS/5.0
		Content-Type: text/html; charset=iso-8859-1
		Content-Length: 32

		Finally, this is the real page!
		HTTP/1.1 401 Sorry wrong password (2)
		Server: Microsoft-IIS/5.0
		Content-Type: text/html; charset=iso-8859-1
		Content-Length: 29
		WWW-Authenticate: Basic realm="testrealm"

		This is a bad password page!
		HTTP/1.1 401 Sorry wrong password (3)
		Server: Microsoft-IIS/5.0
		Content-Type: text/html; charset=iso-8859-1
		Content-Length: 29
		WWW-Authenticate: Basic realm="testrealm"

		This is a bad password page!
		HTTP/1.1 200 Things are fine in server land (2)
		Server: Microsoft-IIS/5.0
		Content-Type: text/html; charset=iso-8859-1
		Content-Length: 32

		Finally, this is the real page!
		</datacheck>

		</reply>

		# Client-side
		<client>
		<server>
		http
		</server>
		<tool>
		libauthretry
		</tool>

		<name>
		HTTP authorization retry (Basic)
		</name>
		<setenv>
		# we force our own host name, in order to make the test machine independent
		CURL_GETHOSTNAME=curlhost
		# we try to use the LD_PRELOAD hack, if not a debug build
		LD_PRELOAD=%PWD/libtest/.libs/libhostname.so
		</setenv>
		<command>
		http://%HOSTIP:%HTTPPORT/2023 basic basic
		</command>
		<precheck>
		chkhostname curlhost
		</precheck>
		</client>

		# Verify data after the test has been "shot"
		<verify>
		<strip>
		^User-Agent:.*
		</strip>
		<protocol>
		GET /20230100 HTTP/1.1
		Authorization: Basic dGVzdHVzZXI6d3JvbmdwYXNz
		Host: %HOSTIP:%HTTPPORT
		Accept: /

		GET /20230200 HTTP/1.1
		Authorization: Basic dGVzdHVzZXI6dGVzdHBhc3M=
		Host: %HOSTIP:%HTTPPORT
		Accept: /

		GET /20230300 HTTP/1.1
		Authorization: Basic dGVzdHVzZXI6d3JvbmdwYXNz
		Host: %HOSTIP:%HTTPPORT
		Accept: /

		GET /20230400 HTTP/1.1
		Authorization: Basic dGVzdHVzZXI6d3JvbmdwYXNz
		Host: %HOSTIP:%HTTPPORT
		Accept: /

		GET /20230500 HTTP/1.1
		Authorization: Basic dGVzdHVzZXI6dGVzdHBhc3M=
		Host: %HOSTIP:%HTTPPORT
		Accept: /

		</protocol>
		</verify>
		</testcase>

tests/data/test2024

0 → 100644

+172 −0

Original line number	Diff line number	Diff line
		<testcase>
		<info>
		<keywords>
		HTTP
		HTTP GET
		HTTP Basic auth
		HTTP Digest auth
		</keywords>
		</info>
		# Server-side
		<reply>

		<!-- Alternate the order that Basic and Digest headers appear in responses to
		ensure that the order doesn't matter. -->

		<!-- First request has Basic auth, wrong password -->
		<data100>
		HTTP/1.1 401 Sorry wrong password
		Server: Microsoft-IIS/5.0
		Content-Type: text/html; charset=iso-8859-1
		Content-Length: 29
		WWW-Authenticate: Digest realm="testrealm", nonce="1"
		WWW-Authenticate: Basic realm="testrealm"

		This is a bad password page!
		</data100>

		<!-- Second request has Digest auth, right password -->
		<data1200>
		HTTP/1.1 200 Things are fine in server land
		Server: Microsoft-IIS/5.0
		Content-Type: text/html; charset=iso-8859-1
		Content-Length: 32

		Finally, this is the real page!
		</data1200>

		<!-- Third request has Basic auth, wrong password -->
		<data300>
		HTTP/1.1 401 Sorry wrong password (2)
		Server: Microsoft-IIS/5.0
		Content-Type: text/html; charset=iso-8859-1
		Content-Length: 29
		WWW-Authenticate: Digest realm="testrealm", nonce="2"
		WWW-Authenticate: Basic realm="testrealm"

		This is a bad password page!
		</data300>

		<!-- Fourth request has Digest auth, wrong password -->
		<data1400>
		HTTP/1.1 401 Sorry wrong password (3)
		Server: Microsoft-IIS/5.0
		Content-Type: text/html; charset=iso-8859-1
		Content-Length: 29
		WWW-Authenticate: Digest realm="testrealm", nonce="3"
		WWW-Authenticate: Basic realm="testrealm"

		This is a bad password page!
		</data1400>

		<!-- Fifth request has Digest auth, right password -->
		<data1500>
		HTTP/1.1 200 Things are fine in server land (2)
		Server: Microsoft-IIS/5.0
		Content-Type: text/html; charset=iso-8859-1
		Content-Length: 32

		Finally, this is the real page!
		</data1500>

		<datacheck>
		HTTP/1.1 401 Sorry wrong password
		Server: Microsoft-IIS/5.0
		Content-Type: text/html; charset=iso-8859-1
		Content-Length: 29
		WWW-Authenticate: Digest realm="testrealm", nonce="1"
		WWW-Authenticate: Basic realm="testrealm"

		This is a bad password page!
		HTTP/1.1 200 Things are fine in server land
		Server: Microsoft-IIS/5.0
		Content-Type: text/html; charset=iso-8859-1
		Content-Length: 32

		Finally, this is the real page!
		HTTP/1.1 401 Sorry wrong password (2)
		Server: Microsoft-IIS/5.0
		Content-Type: text/html; charset=iso-8859-1
		Content-Length: 29
		WWW-Authenticate: Digest realm="testrealm", nonce="2"
		WWW-Authenticate: Basic realm="testrealm"

		This is a bad password page!
		HTTP/1.1 401 Sorry wrong password (3)
		Server: Microsoft-IIS/5.0
		Content-Type: text/html; charset=iso-8859-1
		Content-Length: 29
		WWW-Authenticate: Digest realm="testrealm", nonce="3"
		WWW-Authenticate: Basic realm="testrealm"

		This is a bad password page!
		HTTP/1.1 200 Things are fine in server land (2)
		Server: Microsoft-IIS/5.0
		Content-Type: text/html; charset=iso-8859-1
		Content-Length: 32

		Finally, this is the real page!
		</datacheck>

		</reply>

		# Client-side
		<client>
		<server>
		http
		</server>
		<tool>
		libauthretry
		</tool>

		<name>
		HTTP authorization retry (Basic switching to Digest)
		</name>
		<setenv>
		# we force our own host name, in order to make the test machine independent
		CURL_GETHOSTNAME=curlhost
		# we try to use the LD_PRELOAD hack, if not a debug build
		LD_PRELOAD=%PWD/libtest/.libs/libhostname.so
		</setenv>
		<command>
		http://%HOSTIP:%HTTPPORT/2024 basic digest
		</command>
		<precheck>
		chkhostname curlhost
		</precheck>
		</client>

		# Verify data after the test has been "shot"
		<verify>
		<strip>
		^User-Agent:.*
		</strip>
		<protocol>
		GET /20240100 HTTP/1.1
		Authorization: Basic dGVzdHVzZXI6d3JvbmdwYXNz
		Host: %HOSTIP:%HTTPPORT
		Accept: /

		GET /20240200 HTTP/1.1
		Authorization: Digest username="testuser", realm="testrealm", nonce="1", uri="/20240200", response="ed646c565f79e2dd9fa37cb5a621213c"
		Host: %HOSTIP:%HTTPPORT
		Accept: /

		GET /20240300 HTTP/1.1
		Authorization: Basic dGVzdHVzZXI6d3JvbmdwYXNz
		Host: %HOSTIP:%HTTPPORT
		Accept: /

		GET /20240400 HTTP/1.1
		Authorization: Digest username="testuser", realm="testrealm", nonce="2", uri="/20240400", response="9741ced8caacc6124770187b36f007c5"
		Host: %HOSTIP:%HTTPPORT
		Accept: /

		GET /20240500 HTTP/1.1
		Authorization: Digest username="testuser", realm="testrealm", nonce="3", uri="/20240500", response="5bc77ec8c2d443b27a1b55f1fd8fbb13"
		Host: %HOSTIP:%HTTPPORT
		Accept: /

		</protocol>
		</verify>
		</testcase>

tests/data/test2025

0 → 100644

+268 −0

Original line number	Diff line number	Diff line
		<testcase>
		<info>
		<keywords>
		HTTP
		HTTP GET
		HTTP Basic auth
		HTTP NTLM auth
		</keywords>
		</info>
		# Server-side
		<reply>

		<!-- Alternate the order that Basic and NTLM headers appear in responses to
		ensure that the order doesn't matter. -->

		<!-- First request has Basic auth, wrong password -->
		<data100>
		HTTP/1.1 401 Sorry wrong password
		Server: Microsoft-IIS/5.0
		Content-Type: text/html; charset=iso-8859-1
		Content-Length: 29
		WWW-Authenticate: NTLM
		WWW-Authenticate: Basic realm="testrealm"

		This is a bad password page!
		</data100>

		<!-- Second request has NTLM auth, right password -->
		<data200>
		HTTP/1.1 401 Need Basic or NTLM auth
		Server: Microsoft-IIS/5.0
		Content-Type: text/html; charset=iso-8859-1
		Content-Length: 27
		WWW-Authenticate: Basic realm="testrealm"
		WWW-Authenticate: NTLM

		This is not the real page!
		</data200>

		<data1201>
		HTTP/1.1 401 NTLM intermediate
		Server: Microsoft-IIS/5.0
		Content-Type: text/html; charset=iso-8859-1
		Content-Length: 33
		WWW-Authenticate: NTLM TlRMTVNTUAACAAAACAAIADAAAAAGggEAq6U1NAWaJCIAAAAAAAAAAAAAAAA4AAAATlRMTUF1dGg=

		This is still not the real page!
		</data1201>

		<data1202>
		HTTP/1.1 200 Things are fine in server land
		Server: Microsoft-IIS/5.0
		Content-Type: text/html; charset=iso-8859-1
		Content-Length: 32

		Finally, this is the real page!
		</data1202>

		<!-- Third request has Basic auth, wrong password -->
		<data300>
		HTTP/1.1 401 Sorry wrong password (2)
		Server: Microsoft-IIS/5.0
		Content-Type: text/html; charset=iso-8859-1
		Content-Length: 29
		WWW-Authenticate: NTLM
		WWW-Authenticate: Basic realm="testrealm"

		This is a bad password page!
		</data300>

		<!-- Fourth request has NTLM auth, wrong password -->
		<data400>
		HTTP/1.1 401 Need Basic or NTLM auth (2)
		Server: Microsoft-IIS/5.0
		Content-Type: text/html; charset=iso-8859-1
		Content-Length: 27
		WWW-Authenticate: Basic realm="testrealm"
		WWW-Authenticate: NTLM

		This is not the real page!
		</data400>

		<data1401>
		HTTP/1.1 401 NTLM intermediate (2)
		Server: Microsoft-IIS/5.0
		Content-Type: text/html; charset=iso-8859-1
		Content-Length: 33
		WWW-Authenticate: NTLM TlRMTVNTUAACAAAACAAIADAAAAAGggEAq6U1NAWaJCIAAAAAAAAAAAAAAAA4AAAATlRMTUF1dGg=

		This is still not the real page!
		</data1401>

		<data1402>
		HTTP/1.1 401 Sorry wrong password (3)
		Server: Microsoft-IIS/5.0
		Content-Type: text/html; charset=iso-8859-1
		Content-Length: 29
		WWW-Authenticate: NTLM
		WWW-Authenticate: Basic realm="testrealm"

		This is a bad password page!
		</data1402>

		<!-- Fifth request has NTLM auth, right password -->
		<data500>
		HTTP/1.1 401 Need Basic or NTLM auth (3)
		Server: Microsoft-IIS/5.0
		Content-Type: text/html; charset=iso-8859-1
		Content-Length: 27
		WWW-Authenticate: Basic realm="testrealm"
		WWW-Authenticate: NTLM

		This is not the real page!
		</data500>

		<data1501>
		HTTP/1.1 401 NTLM intermediate (3)
		Server: Microsoft-IIS/5.0
		Content-Type: text/html; charset=iso-8859-1
		Content-Length: 33
		WWW-Authenticate: NTLM TlRMTVNTUAACAAAACAAIADAAAAAGggEAq6U1NAWaJCIAAAAAAAAAAAAAAAA4AAAATlRMTUF1dGg=

		This is still not the real page!
		</data1501>

		<data1502>
		HTTP/1.1 200 Things are fine in server land (2)
		Server: Microsoft-IIS/5.0
		Content-Type: text/html; charset=iso-8859-1
		Content-Length: 32

		Finally, this is the real page!
		</data1502>

		<datacheck>
		HTTP/1.1 401 Sorry wrong password
		Server: Microsoft-IIS/5.0
		Content-Type: text/html; charset=iso-8859-1
		Content-Length: 29
		WWW-Authenticate: NTLM
		WWW-Authenticate: Basic realm="testrealm"

		This is a bad password page!
		HTTP/1.1 401 NTLM intermediate
		Server: Microsoft-IIS/5.0
		Content-Type: text/html; charset=iso-8859-1
		Content-Length: 33
		WWW-Authenticate: NTLM TlRMTVNTUAACAAAACAAIADAAAAAGggEAq6U1NAWaJCIAAAAAAAAAAAAAAAA4AAAATlRMTUF1dGg=

		HTTP/1.1 200 Things are fine in server land
		Server: Microsoft-IIS/5.0
		Content-Type: text/html; charset=iso-8859-1
		Content-Length: 32

		Finally, this is the real page!
		HTTP/1.1 401 Sorry wrong password (2)
		Server: Microsoft-IIS/5.0
		Content-Type: text/html; charset=iso-8859-1
		Content-Length: 29
		WWW-Authenticate: NTLM
		WWW-Authenticate: Basic realm="testrealm"

		This is a bad password page!
		HTTP/1.1 401 NTLM intermediate (2)
		Server: Microsoft-IIS/5.0
		Content-Type: text/html; charset=iso-8859-1
		Content-Length: 33
		WWW-Authenticate: NTLM TlRMTVNTUAACAAAACAAIADAAAAAGggEAq6U1NAWaJCIAAAAAAAAAAAAAAAA4AAAATlRMTUF1dGg=

		HTTP/1.1 401 Sorry wrong password (3)
		Server: Microsoft-IIS/5.0
		Content-Type: text/html; charset=iso-8859-1
		Content-Length: 29
		WWW-Authenticate: NTLM
		WWW-Authenticate: Basic realm="testrealm"

		This is a bad password page!
		HTTP/1.1 401 NTLM intermediate (3)
		Server: Microsoft-IIS/5.0
		Content-Type: text/html; charset=iso-8859-1
		Content-Length: 33
		WWW-Authenticate: NTLM TlRMTVNTUAACAAAACAAIADAAAAAGggEAq6U1NAWaJCIAAAAAAAAAAAAAAAA4AAAATlRMTUF1dGg=

		HTTP/1.1 200 Things are fine in server land (2)
		Server: Microsoft-IIS/5.0
		Content-Type: text/html; charset=iso-8859-1
		Content-Length: 32

		Finally, this is the real page!
		</datacheck>

		</reply>

		# Client-side
		<client>
		<server>
		http
		</server>
		<tool>
		libauthretry
		</tool>

		<name>
		HTTP authorization retry (Basic switching to NTLM)
		</name>
		<setenv>
		# we force our own host name, in order to make the test machine independent
		CURL_GETHOSTNAME=curlhost
		# we try to use the LD_PRELOAD hack, if not a debug build
		LD_PRELOAD=%PWD/libtest/.libs/libhostname.so
		</setenv>
		<command>
		http://%HOSTIP:%HTTPPORT/2025 basic ntlm
		</command>
		<precheck>
		chkhostname curlhost
		</precheck>
		</client>

		# Verify data after the test has been "shot"
		<verify>
		<strip>
		^User-Agent:.*
		</strip>
		<protocol>
		GET /20250100 HTTP/1.1
		Authorization: Basic dGVzdHVzZXI6d3JvbmdwYXNz
		Host: %HOSTIP:%HTTPPORT
		Accept: /

		GET /20250200 HTTP/1.1
		Authorization: NTLM TlRMTVNTUAABAAAABoIIAAAAAAAAAAAAAAAAAAAAAAA=
		Host: %HOSTIP:%HTTPPORT
		Accept: /

		GET /20250200 HTTP/1.1
		Authorization: NTLM TlRMTVNTUAADAAAAGAAYAEAAAAAYABgAWAAAAAAAAABwAAAACAAIAHAAAAAIAAgAeAAAAAAAAAAAAAAABoIBAI+/Fp9IERAQ74OsdNPbBpg7o8CVwLSO4DtFyIcZHUMKVktWIu92s2892OVpd2JzqnRlc3R1c2VyY3VybGhvc3Q=
		Host: %HOSTIP:%HTTPPORT
		Accept: /

		GET /20250300 HTTP/1.1
		Authorization: Basic dGVzdHVzZXI6d3JvbmdwYXNz
		Host: %HOSTIP:%HTTPPORT
		Accept: /

		GET /20250400 HTTP/1.1
		Authorization: NTLM TlRMTVNTUAABAAAABoIIAAAAAAAAAAAAAAAAAAAAAAA=
		Host: %HOSTIP:%HTTPPORT
		Accept: /

		GET /20250400 HTTP/1.1
		Authorization: NTLM TlRMTVNTUAADAAAAGAAYAEAAAAAYABgAWAAAAAAAAABwAAAACAAIAHAAAAAIAAgAeAAAAAAAAAAAAAAABoIBANgKEcT5xUUBHw5+0m4FjWTGNzg6PeHJHbaPwNwCt/tXcnIeTQCTMAg12SPDyNXMf3Rlc3R1c2VyY3VybGhvc3Q=
		Host: %HOSTIP:%HTTPPORT
		Accept: /

		GET /20250500 HTTP/1.1
		Authorization: NTLM TlRMTVNTUAABAAAABoIIAAAAAAAAAAAAAAAAAAAAAAA=
		Host: %HOSTIP:%HTTPPORT
		Accept: /

		GET /20250500 HTTP/1.1
		Authorization: NTLM TlRMTVNTUAADAAAAGAAYAEAAAAAYABgAWAAAAAAAAABwAAAACAAIAHAAAAAIAAgAeAAAAAAAAAAAAAAABoIBAI+/Fp9IERAQ74OsdNPbBpg7o8CVwLSO4DtFyIcZHUMKVktWIu92s2892OVpd2JzqnRlc3R1c2VyY3VybGhvc3Q=
		Host: %HOSTIP:%HTTPPORT
		Accept: /

		</protocol>
		</verify>
		</testcase>

tests/data/test2026

0 → 100644

+216 −0

Original line number	Diff line number	Diff line
		<testcase>
		<info>
		<keywords>
		HTTP
		HTTP GET
		HTTP Basic auth
		HTTP Digest auth
		</keywords>
		</info>
		# Server-side
		<reply>

		<!-- Alternate the order that Basic and Digest headers appear in responses to
		ensure that the order doesn't matter. -->

		<!-- First request has Digest auth, wrong password -->
		<data100>
		HTTP/1.1 401 Need Basic or Digest auth
		Server: Microsoft-IIS/5.0
		Content-Type: text/html; charset=iso-8859-1
		Content-Length: 27
		WWW-Authenticate: Digest realm="testrealm", nonce="1"
		WWW-Authenticate: Basic realm="testrealm"

		This is not the real page!
		</data100>

		<data1100>
		HTTP/1.1 401 Sorry wrong password
		Server: Microsoft-IIS/5.0
		Content-Type: text/html; charset=iso-8859-1
		Content-Length: 29
		WWW-Authenticate: Basic realm="testrealm"
		WWW-Authenticate: Digest realm="testrealm", nonce="2"

		This is a bad password page!
		</data1100>

		<!-- Second request has Basic auth, right password -->
		<data200>
		HTTP/1.1 200 Things are fine in server land
		Server: Microsoft-IIS/5.0
		Content-Type: text/html; charset=iso-8859-1
		Content-Length: 32

		Finally, this is the real page!
		</data200>

		<!-- Third request has Digest auth, wrong password -->
		<data300>
		HTTP/1.1 401 Need Basic or Digest auth (2)
		Server: Microsoft-IIS/5.0
		Content-Type: text/html; charset=iso-8859-1
		Content-Length: 27
		WWW-Authenticate: Digest realm="testrealm", nonce="3"
		WWW-Authenticate: Basic realm="testrealm"

		This is not the real page!
		</data300>

		<data1300>
		HTTP/1.1 401 Sorry wrong password (2)
		Server: Microsoft-IIS/5.0
		Content-Type: text/html; charset=iso-8859-1
		Content-Length: 29
		WWW-Authenticate: Basic realm="testrealm"
		WWW-Authenticate: Digest realm="testrealm", nonce="4"

		This is a bad password page!
		</data1300>

		<!-- Fourth request has Basic auth, wrong password -->
		<data400>
		HTTP/1.1 401 Sorry wrong password (3)
		Server: Microsoft-IIS/5.0
		Content-Type: text/html; charset=iso-8859-1
		Content-Length: 29
		WWW-Authenticate: Digest realm="testrealm", nonce="5"
		WWW-Authenticate: Basic realm="testrealm"

		This is a bad password page!
		</data400>

		<!-- Fifth request has Basic auth, right password -->
		<data500>
		HTTP/1.1 200 Things are fine in server land (2)
		Server: Microsoft-IIS/5.0
		Content-Type: text/html; charset=iso-8859-1
		Content-Length: 32

		Finally, this is the real page!
		</data500>

		<datacheck>
		HTTP/1.1 401 Need Basic or Digest auth
		Server: Microsoft-IIS/5.0
		Content-Type: text/html; charset=iso-8859-1
		Content-Length: 27
		WWW-Authenticate: Digest realm="testrealm", nonce="1"
		WWW-Authenticate: Basic realm="testrealm"

		HTTP/1.1 401 Sorry wrong password
		Server: Microsoft-IIS/5.0
		Content-Type: text/html; charset=iso-8859-1
		Content-Length: 29
		WWW-Authenticate: Basic realm="testrealm"
		WWW-Authenticate: Digest realm="testrealm", nonce="2"

		This is a bad password page!
		HTTP/1.1 200 Things are fine in server land
		Server: Microsoft-IIS/5.0
		Content-Type: text/html; charset=iso-8859-1
		Content-Length: 32

		Finally, this is the real page!
		HTTP/1.1 401 Need Basic or Digest auth (2)
		Server: Microsoft-IIS/5.0
		Content-Type: text/html; charset=iso-8859-1
		Content-Length: 27
		WWW-Authenticate: Digest realm="testrealm", nonce="3"
		WWW-Authenticate: Basic realm="testrealm"

		HTTP/1.1 401 Sorry wrong password (2)
		Server: Microsoft-IIS/5.0
		Content-Type: text/html; charset=iso-8859-1
		Content-Length: 29
		WWW-Authenticate: Basic realm="testrealm"
		WWW-Authenticate: Digest realm="testrealm", nonce="4"

		This is a bad password page!
		HTTP/1.1 401 Sorry wrong password (3)
		Server: Microsoft-IIS/5.0
		Content-Type: text/html; charset=iso-8859-1
		Content-Length: 29
		WWW-Authenticate: Digest realm="testrealm", nonce="5"
		WWW-Authenticate: Basic realm="testrealm"

		This is a bad password page!
		HTTP/1.1 200 Things are fine in server land (2)
		Server: Microsoft-IIS/5.0
		Content-Type: text/html; charset=iso-8859-1
		Content-Length: 32

		Finally, this is the real page!
		</datacheck>

		</reply>

		# Client-side
		<client>
		<server>
		http
		</server>
		<tool>
		libauthretry
		</tool>

		<name>
		HTTP authorization retry (Digest switching to Basic)
		</name>
		<setenv>
		# we force our own host name, in order to make the test machine independent
		CURL_GETHOSTNAME=curlhost
		# we try to use the LD_PRELOAD hack, if not a debug build
		LD_PRELOAD=%PWD/libtest/.libs/libhostname.so
		</setenv>
		<command>
		http://%HOSTIP:%HTTPPORT/2026 digest basic
		</command>
		<precheck>
		chkhostname curlhost
		</precheck>
		</client>

		# Verify data after the test has been "shot"
		<verify>
		<strip>
		^User-Agent:.*
		</strip>
		<protocol>
		GET /20260100 HTTP/1.1
		Host: %HOSTIP:%HTTPPORT
		Accept: /

		GET /20260100 HTTP/1.1
		Authorization: Digest username="testuser", realm="testrealm", nonce="1", uri="/20260100", response="5f992a2e761ab926256419f7c685f85b"
		Host: %HOSTIP:%HTTPPORT
		Accept: /

		GET /20260200 HTTP/1.1
		Authorization: Basic dGVzdHVzZXI6dGVzdHBhc3M=
		Host: %HOSTIP:%HTTPPORT
		Accept: /

		GET /20260300 HTTP/1.1
		Host: %HOSTIP:%HTTPPORT
		Accept: /

		GET /20260300 HTTP/1.1
		Authorization: Digest username="testuser", realm="testrealm", nonce="3", uri="/20260300", response="132242e602882251929be93228c830ae"
		Host: %HOSTIP:%HTTPPORT
		Accept: /

		GET /20260400 HTTP/1.1
		Authorization: Basic dGVzdHVzZXI6d3JvbmdwYXNz
		Host: %HOSTIP:%HTTPPORT
		Accept: /

		GET /20260500 HTTP/1.1
		Authorization: Basic dGVzdHVzZXI6dGVzdHBhc3M=
		Host: %HOSTIP:%HTTPPORT
		Accept: /

		</protocol>
		</verify>
		</testcase>