Revision: 14828
Author: adrian.chadd
Date: Fri Nov 26 20:49:22 2010
Log: Issue #134 - since I'm seeing status codes > 999 in the wild, bump the
invalid
status code value to something a bit higher.
This doesn't fix the client-side hanging that occurs in this instance, but
it
does hide the problem from the normal case.
http://code.google.com/p/lusca-cache/source/detail?r=14828
Modified:
/branches/LUSCA_HEAD/libhttp/HttpStatusLine.h
=======================================
--- /branches/LUSCA_HEAD/libhttp/HttpStatusLine.h Sat Jun 7 20:17:44 2008
+++ /branches/LUSCA_HEAD/libhttp/HttpStatusLine.h Fri Nov 26 20:49:22 2010
@@ -48,8 +48,9 @@
HTTP_GATEWAY_TIMEOUT = 504,
HTTP_HTTP_VERSION_NOT_SUPPORTED = 505,
HTTP_INSUFFICIENT_STORAGE = 507, /* RFC2518 section 10.6 */
- HTTP_INVALID_HEADER = 600, /* Squid header parsing error */
- HTTP_HEADER_TOO_LARGE = 601 /* Header too large to process */
+
+ HTTP_INVALID_HEADER = 1001, /* Squid header parsing error */
+ HTTP_HEADER_TOO_LARGE = 1002 /* Header too large to process */
} http_status;
/* http status line */
--
You received this message because you are subscribed to the Google Groups
"lusca-commit" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/lusca-commit?hl=en.
