Bug 2085: Support ICAP 201 responses. Treat them as ICAP 200.

Symantec Scan Engine 5.0 and later is using ICAP 201 response to
indicate that it has modified the virgin HTTP message. Squid currently
does not care.

diff --git a/src/ICAP/ICAPModXact.cc b/src/ICAP/ICAPModXact.cc
index 0c92672cd6a62848289e6570dfbc170464e23574..99324cab8455e340b89885f6fc2c8910a007dba3 100644 (file)
--- a/src/ICAP/ICAPModXact.cc
+++ b/src/ICAP/ICAPModXact.cc
@@ -696,6 +696,7 @@ void ICAPModXact::parseIcapHead()
         break;
 
     case 200:
+    case 201: // Symantec Scan Engine 5.0 and later when modifying HTTP msg
 
         if (!validate200Ok()) {
             throw TexcHere("Invalid ICAP Response");
@@ -719,8 +720,6 @@ void ICAPModXact::parseIcapHead()
     // Non-100 status means the server needs no postPreview data from us.
     if (state.writing == State::writingPaused)
         stopWriting(true);
-
-    // TODO: Consider applying a Squid 2.5 patch to recognize 201 responses
 }
 
 bool ICAPModXact::validate200Ok()