tolerate CGI scripts which either ignore request content data in part or whole and also cope with request content data in anything other than a POST request: send such content data to the CGI script too, just don't barf a fatal HTTP 5xx hairball when there's no content to be sent (and the request isn't POST or PUT). Bottom line: contrary to before, CGI scripts can now silently ignore content data waiting on their stdin channel and still produce HTTP 200 OK responses if they can/want.
tolerate CGI scripts which either ignore request content data in part or whole and also cope with request content data in anything other than a POST request: send such content data to the CGI script too, just don't barf a fatal HTTP 5xx hairball when there's no content to be sent (and the request isn't POST or PUT).
Bottom line: contrary to before, CGI scripts can now silently ignore content data waiting on their stdin channel and still produce HTTP 200 OK responses if they can/want.

GerHobbelt/civet-webserver,GerHobbelt/civet-webserver,commshare/civet-webserver,GerHobbelt/civet-webserver,commshare/civet-webserver,commshare/civet-webserver,commshare/civet-webserver,GerHobbelt/civet-webserver,commshare/civet-webserver,GerHobbelt/civet-webserver,commshare/civet-webserver,GerHobbelt/civet-webserver,commshare/civet-webserver