12.07.2015 Views

WSM Reference Guide - WatchGuard Technologies

WSM Reference Guide - WatchGuard Technologies

WSM Reference Guide - WatchGuard Technologies

SHOW MORE
SHOW LESS
  • No tags were found...

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Traffic LogsHTTP Proxy Traffic Log MessagesText in Message FieldAssociated FieldsHTTP INTERNAL ERRORHTTP SERVER RESPONSE TIMEOUTHTTP CLIENT REQUEST TIMEOUTHTTP CLOSE COMPLETE TIMEOUTHTTP START LINE OVERSIZEHTTP REQUEST LINE PARSE ERRORlineHTTP STATUS LINE PARSE ERRORlineHTTP HEADER LINE OVERSIZElineHTTP HEADER BLOCK OVERSIZElineHTTP HEADER BLOCK PARSE ERRORHTTP REQUEST URL PATH MISSINGlineHTTP REQUEST URL MATCHrulenamedstnameargHTTP CHUNK SIZE LINE OVERSIZElineHTTP CHUNK SIZE INVALIDlineHTTP CHUNK CRLF TAIL MISSINGlineHTTP FOOTER LINE OVERSIZElineHTTP FOOTER BLOCK OVERSIZElineHTTP FOOTER BLOCK PARSE ERRORHTTP BODY CONTENT TYPE MATCHrulenameHTTP HEADER MALFORMEDlineHTTP HEADER CONTENT LENGTH INVALIDMessage MeaningValue that appears in associated field(s)The HTTP server did not send a response before the configured timeoutThe HTTP client did not send a request before the configured time-outThe remote host did not promptly complete the closing of the TCPconnection.The first line of the HTTP request or response is larger than theconfigured limit (maximum header line length).The first line of the HTTP request is not in the correct format.header line that caused errorThe first line of the HTTP response is not in the correct format.status line that caused errorThe length of an individual header is greater than the configured limit.header line that exceeded the limitThe total length of all headers for a request or response is greater thanthe configured limit.header line that exceeded the limitThe HTTP header block is not in the correct format.The HTTP request does not include a URL path.request line that caused errorThe HTTP request includes a URL specified in the proxy ruleset.name of rule matched in rulesethost name from requested URLpath and query-string from requested URLThe line setting the size of the next response data chunk has a valuethat is too big.request line that caused errorThe line setting the size of the next response data chunk has an invalidvalue.request line that caused errorThe “carriage-return/line-feed” (CRLF) at the end of a data chunk is notthere.the line that caused the errorThe length of an individual footer line is greater than the configuredlimit.request line that exceeded the limitThe total length of all footers for a request or response is greater thanthe configured limit..footer line that exceeded the limitThe HTTP footer block is not in the correct format.The content type in the response body matches a type configured inthe proxy rule set.name of rule matched in rulesetAn individual HTTP header is not in the correct format.the line with the malformed headerThe Content-Length response header value is not a valid number.34 <strong>WatchGuard</strong> System Manager

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!