From c67a99ff27036c824be15f01e21b91c3ec08da4a Mon Sep 17 00:00:00 2001 From: Daniel Stenberg Date: Fri, 29 Aug 2008 10:47:59 +0000 Subject: - When libcurl was doing a HTTP POST and the server would respond with "Connection: close" and actually close the connection after the response-body, libcurl could still have outstanding data to send and it would not properly notice this and stop sending. This caused weirdness and sad faces. http://curl.haxx.se/bug/view.cgi?id=2080222 Note that there are still reasons to consider libcurl's behavior when getting a >= 400 response code while sending data, as Craig Perras' note "http upload: how to stop on error" specifies: http://curl.haxx.se/mail/archive-2008-08/0138.html --- tests/FILEFORMAT | 10 ++++++---- 1 file changed, 6 insertions(+), 4 deletions(-) (limited to 'tests/FILEFORMAT') diff --git a/tests/FILEFORMAT b/tests/FILEFORMAT index 555cee52d..e4be47ab4 100644 --- a/tests/FILEFORMAT +++ b/tests/FILEFORMAT @@ -113,12 +113,14 @@ PASVBADIP - makes PASV send back an illegal IP in its 227 response For HTTP/HTTPS: -auth_required - if this is set and a POST/PUT is made without auth, the +auth_required if this is set and a POST/PUT is made without auth, the server will NOT wait for the full request body to get sent -idle - do nothing after receiving the request, just "sit idle" -stream - continuously send data to the client, never-ending -pipe: [num] - tell the server to expect this many HTTP requests before +idle do nothing after receiving the request, just "sit idle" +stream continuously send data to the client, never-ending +pipe: [num] tell the server to expect this many HTTP requests before sending back anything, to allow pipelining tests +skip: [num] instructs the server to ignore reading this many bytes from a PUT + or POST request -- cgit v1.2.3