From: Luca Toscano Date: Mon, 1 Aug 2016 11:24:44 +0000 (+0000) Subject: Changed the code comments to be more clear a fixed a typo (will be more careful next... X-Git-Tag: 2.5.0-alpha~1347 X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=ef144aed6fe6c4310c5ce041265d4f1d862f09b0;p=thirdparty%2Fapache%2Fhttpd.git Changed the code comments to be more clear a fixed a typo (will be more careful next time, didn't spot the problem until already committed) git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@1754736 13f79535-47bb-0310-9956-ffa450edef68 --- diff --git a/modules/proxy/mod_proxy_fcgi.c b/modules/proxy/mod_proxy_fcgi.c index 53455322b13..2fc0801ef39 100644 --- a/modules/proxy/mod_proxy_fcgi.c +++ b/modules/proxy/mod_proxy_fcgi.c @@ -663,16 +663,15 @@ recv_again: else if (status == HTTP_NOT_MODIFIED) { /* A 304 response MUST NOT contain * a message-body, so we must ignore it but - * some extra steps needs to be taken to + * some extra steps need to be taken to * avoid inconsistencies. * The break is not added with connection * reuse set since there might be more bytes - * to read from the FCGI connection, - * like the message-body, that would trigger - * subsequent bogus reads (for example + * to read like the message-body, that would + * trigger subsequent bogus reads (for example * the start of the message-body - * interpreted as FCGI header). - * With connecton reuse disabled (default) + * interpreted as a FCGI header). + * With connection reuse disabled (default) * we can safely break and force the end * of the FCGI processing phase since the * connection will be cleaned up later on. */