On 09/29/2010 02:20 AM, Mark Nottingham wrote:
How does this interact with<http://trac.tools.ietf.org/wg/httpbis/trac/ticket/29>?
I do not know for sure (even though I think I wrote that ticket precursor!), but I suspect more fixes will be needed to address ticket #29. Glad that RFC bug is going to be fixed though -- I did not get very optimistic responses when it was initially reported...
In general, we are focusing on RFC 2616 compliance for now, unless HTTPbis can reduce the amount of work needed.
While you're at it, any thoughts about<http://trac.tools.ietf.org/wg/httpbis/trac/ticket/212>?
It sounds like you are proposing a general "the path to origin is all HTTP/1.1" test. If yes, it should be documented separately and used throughout the specs as needed, IMHO.
Thank you, Alex.
On 28/09/2010, at 3:01 PM, Alex Rousskov wrote:HTTP Compliance: improve entity age calculation. Account for response delay in entity age calculation as described in RFC 2616 section 13.2.3. Co-Advisor test cases: test_case/rfc2616/ageCalc-none-7-none test_case/rfc2616/ageCalc-5400-4-5-- Mark Nottingham [email protected]
