These statistics are only available when the
--showResponseCodes flag is enabled.
========================================================================= == Response Codes ========================================================================= ----- Response Code: 200 ----- Number of Requests: 929698 (99.948%) Avg Response Time (ms): 362.699 Avg Engine Time (ms): 44.742 Avg Response Size (bytes): 507214.896 Request Times over 1250 ms: 34070 (3.665%) Engine Times over 750 ms: 1213 (0.130%) ----- Response Code: 404 ----- Number of Requests: 484 (0.052%) Avg Response Time (ms): 902.004 Avg Engine Time (ms): 2.147 Avg Response Size (bytes): 10723.893 Request Times over 1250 ms: 150 (30.992%) Engine Times over 750 ms: 0 (0.000%)
This section displays statistics categorized by the HTTP response code returned by the MDEX Engine for each query. The sum of the percentages of each response code should equal 100% (accounting for rounding), since any one query can only produce a single response code.
The following are the most common response codes produced by an MDEX Engine:
404: Not Found. The query sent to the MDEX Engine was in an incomprehensible format (e.g. "/favicon.ico"), or the query specified a navigation descriptor that does not exist. The most common causes of 404s are browser bookmarks/favorites that are no longer valid, direct browser queries to the MDEX Engine that produce favicon requests, and typos.
408: Request Timeout. The client that produced the request (typically the Endeca API) went away before the MDEX Engine could write the response to it. Typically this means that the request took a very long time to complete and the requesting application timed out before the MDEX Engine returned a response. Empty requests also often generate 408 codes.
For more information on HTTP response codes, see RFC2616 (Hypertext Transfer Protocol) and elsewhere.
