You are viewing a plain text version of this content. The canonical link for it is here.
Posted to cvs@httpd.apache.org by el...@apache.org on 2016/08/01 11:24:44 UTC

svn commit: r1754736 - /httpd/httpd/trunk/modules/proxy/mod_proxy_fcgi.c

Author: elukey
Date: Mon Aug  1 11:24:44 2016
New Revision: 1754736

URL: http://svn.apache.org/viewvc?rev=1754736&view=rev
Log:
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)

Modified:
    httpd/httpd/trunk/modules/proxy/mod_proxy_fcgi.c

Modified: httpd/httpd/trunk/modules/proxy/mod_proxy_fcgi.c
URL: http://svn.apache.org/viewvc/httpd/httpd/trunk/modules/proxy/mod_proxy_fcgi.c?rev=1754736&r1=1754735&r2=1754736&view=diff
==============================================================================
--- httpd/httpd/trunk/modules/proxy/mod_proxy_fcgi.c (original)
+++ httpd/httpd/trunk/modules/proxy/mod_proxy_fcgi.c Mon Aug  1 11:24:44 2016
@@ -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. */