- better comments for httpHdrRangeWillBeComplex + HIT case

diff --git a/src/client_side.cc b/src/client_side.cc
index cc2161945cef56d31f3746a3c7782fd2c006e3d8..a6077b95cc466b5257882f2cb99e0f1ec0ab9748 100644 (file)
--- a/src/client_side.cc
+++ b/src/client_side.cc
@@ -1,6 +1,6 @@
 
 /*
- * $Id: client_side.cc,v 1.403 1998/09/29 16:33:43 wessels Exp $
+ * $Id: client_side.cc,v 1.404 1998/09/29 23:53:27 rousskov Exp $
  *
  * DEBUG: section 33    Client-side Routines
  * AUTHOR: Duane Wessels
@@ -1622,8 +1622,9 @@ clientProcessRequest2(clientHttpRequest * http)
        ipcacheReleaseInvalid(r->host);
        return LOG_TCP_CLIENT_REFRESH_MISS;
     } else if (r->range && httpHdrRangeWillBeComplex(r->range)) {
-       /* some clients break if we return "200 OK" for a Range request
-        * and we _will_ return 200 if ranges happen to bee too complex */
+       /* Some clients break if we return "200 OK" for a Range request.
+        * We would have to return "200 OK" for a _complex_ Range request
+        * that is also a HIT. Thus, let's prevent HITs on complex Range requests */
        http->entry = NULL;
        return LOG_TCP_MISS;
     } else {