1a36923d73
- Change the swsbounce keyword to override the part number on a subsequent request to the previous part number + 1. Note the previous part number in this case is the part number that was returned as a response to the previous request and contained the swsbounce keyword. Prior to this change swsbounce incremented the part number of the subsequent request instead of overriding it, and did so in a more limited fashion that prevented chaining swsbounce in multiple responses. For example, if the test makes a request that causes the sws server to return `<data>` as a response and that response contains `swsbounce` then for the next response the sws server returns `<data1>`. If `<data1>` also contains `swsbounce` then for the next response the sws server now returns `<data2>` instead of the requested part. Fixes https://github.com/curl/curl/discussions/16074 Closes https://github.com/curl/curl/pull/16085
96 lines
1.9 KiB
Plaintext
96 lines
1.9 KiB
Plaintext
<testcase>
|
|
<info>
|
|
<keywords>
|
|
HTTP
|
|
HTTP PUT
|
|
HTTP Digest auth
|
|
</keywords>
|
|
</info>
|
|
|
|
# Server-side
|
|
<reply>
|
|
<data>
|
|
HTTP/1.1 401 authentication please
|
|
Server: Microsoft-IIS/6.0
|
|
WWW-Authenticate: Digest realm="testrealm", nonce="1053604144"
|
|
Content-Type: text/html; charset=iso-8859-1
|
|
Content-Length: 0
|
|
|
|
</data>
|
|
<data1000>
|
|
HTTP/1.1 200 A OK
|
|
Server: Microsoft-IIS/6.0
|
|
Content-Type: text/html; charset=iso-8859-1
|
|
Content-Length: 3
|
|
|
|
ok
|
|
</data1000>
|
|
|
|
<datacheck>
|
|
HTTP/1.1 401 authentication please
|
|
Server: Microsoft-IIS/6.0
|
|
WWW-Authenticate: Digest realm="testrealm", nonce="1053604144"
|
|
Content-Type: text/html; charset=iso-8859-1
|
|
Content-Length: 0
|
|
|
|
HTTP/1.1 200 A OK
|
|
Server: Microsoft-IIS/6.0
|
|
Content-Type: text/html; charset=iso-8859-1
|
|
Content-Length: 3
|
|
|
|
ok
|
|
</datacheck>
|
|
|
|
</reply>
|
|
|
|
# Client-side
|
|
<client>
|
|
#
|
|
<server>
|
|
http
|
|
</server>
|
|
<features>
|
|
!SSPI
|
|
crypto
|
|
</features>
|
|
<name>
|
|
HTTP PUT --digest with user-specified Content-Length header
|
|
</name>
|
|
# This test is to ensure 'Content-Length: 0' is sent while negotiating auth
|
|
# even when there is a user-specified Content-Length header.
|
|
# https://github.com/curl/curl/pull/1242
|
|
<command>
|
|
-H "Content-Length: 85" -u auser:apasswd --digest -T %LOGDIR/put%TESTNUMBER http://%HOSTIP:%HTTPPORT/%TESTNUMBER
|
|
</command>
|
|
<file name="%LOGDIR/put%TESTNUMBER">
|
|
This is data we upload with PUT
|
|
a second line
|
|
line three
|
|
four is the number of lines
|
|
</file>
|
|
</client>
|
|
|
|
# Verify data after the test has been "shot"
|
|
<verify>
|
|
<protocol>
|
|
PUT /%TESTNUMBER HTTP/1.1
|
|
Host: %HOSTIP:%HTTPPORT
|
|
User-Agent: curl/%VERSION
|
|
Accept: */*
|
|
Content-Length: 0
|
|
|
|
PUT /%TESTNUMBER HTTP/1.1
|
|
Host: %HOSTIP:%HTTPPORT
|
|
Authorization: Digest username="auser", realm="testrealm", nonce="1053604144", uri="/%TESTNUMBER", response="dc185587d5e8391b347eef194c2a3cd6"
|
|
User-Agent: curl/%VERSION
|
|
Accept: */*
|
|
Content-Length: 85
|
|
|
|
This is data we upload with PUT
|
|
a second line
|
|
line three
|
|
four is the number of lines
|
|
</protocol>
|
|
</verify>
|
|
</testcase>
|