Below is a list of a few test cases that failed when we ran CoAdvisor on ATS (3.2) :
Test Case Configurable issue? DUT MUST handle "chunked" response with bad Content-Length header sent to an HTTP/1.0 client proxy MUST NOT forward epilogue in multipart/byteranges response proxy MUST NOT forward epilogue in multipart/byteranges request proxy MUST NOT forward Trailer respond header proxy MUST NOT forward Trailer request header servers MUST respond with a 400 status code to 1.1 requests without Host header client MUST accept 1 4-header 101-status response(s) prior to a regular response client MUST accept 1 4-header 199-status response(s) prior to a regular response proxy MUST forward 1 4-header 101-status response(s) prior to a regular response proxy MUST forward 1 4-header 199-status response(s) prior to a regular response proxy MUST respond with 417 (Expectation Failed) if it cannot meet the "0100-continue" expectation proxy MUST respond with 417 (Expectation Failed) if it cannot meet the "100-continueing" expectation proxy MUST respond with 417 (Expectation Failed) if it cannot meet the "expect=params" expectation proxy MUST respond with 417 (Expectation Failed) if it cannot meet the "expect=" 100-continue="" expectation 1. We wanted to know whether what we see is a configuration issue or a bug on ATS. 2. If it's a bug, How "bad" is it? Is this bug a serious compatibility issue or a rare corner case ? We will extremely appreciate if someone could help us with one test case or more ... (Once we will remove private data from the CoAdvisor report we will send the full report to anyone who wishes it.) Thanks, Jacob
