Hello,
HTTP compliance results for Squid 3.0.23, 3.1.16, and trunk r10264
have been uploaded to http://wiki.squid-cache.org/Features/HTTP11
We tried to preserve the old results intact for this update and just
added new stuff. Going forward, we will polish the spreadsheet and
probably remove
On 01/28/2010 04:42 PM, Mark Nottingham wrote:
FWIW, I have an XSLT stylesheet that can format the results
pleasantly; it could be a starting point for something automated.
Please share if you can.
Thank you,
Alex.
On 29/01/2010, at 12:34 AM, Amos Jeffries wrote:
Robert Collins wrote:
On 01/28/2010 06:34 AM, Amos Jeffries wrote:
Robert Collins wrote:
On Wed, 2010-01-27 at 22:49 -0700, Alex Rousskov wrote:
c) Co-Advisor currently only tests MUST-level requirements. Old Robert's
checklist contained some SHOULD-level requirements as well. I see that
Sheet1 on the
On Wed, 2010-01-27 at 22:49 -0700, Alex Rousskov wrote:
c) Co-Advisor currently only tests MUST-level requirements. Old Robert's
checklist contained some SHOULD-level requirements as well. I see that
Sheet1 on the spreadsheet has SHOULDs. Are we kind of ignoring them (and
Sheet1) for now,
Robert Collins wrote:
On Wed, 2010-01-27 at 22:49 -0700, Alex Rousskov wrote:
c) Co-Advisor currently only tests MUST-level requirements. Old Robert's
checklist contained some SHOULD-level requirements as well. I see that
Sheet1 on the spreadsheet has SHOULDs. Are we kind of ignoring them
FWIW, I have an XSLT stylesheet that can format the results pleasantly; it
could be a starting point for something automated.
On 29/01/2010, at 12:34 AM, Amos Jeffries wrote:
Robert Collins wrote:
On Wed, 2010-01-27 at 22:49 -0700, Alex Rousskov wrote:
c) Co-Advisor currently only tests
On 01/09/2010 04:10 AM, Amos Jeffries wrote:
Alex Rousskov wrote:
On 09/12/2009 05:36 AM, Amos Jeffries wrote:
Updating the checklist today I again wonder if we can repeat the step
from 2.7 and enable HTTP/1.1 on requests sent to servers
As far as I can see the missing bits 3.2 needs to take
Alex Rousskov wrote:
On 09/12/2009 05:36 AM, Amos Jeffries wrote:
Updating the checklist today I again wonder if we can repeat the step
from 2.7 and enable HTTP/1.1 on requests sent to servers
As far as I can see the missing bits 3.2 needs to take that step are:
- reject http-Upgrade
On 09/12/2009 05:36 AM, Amos Jeffries wrote:
Updating the checklist today I again wonder if we can repeat the step
from 2.7 and enable HTTP/1.1 on requests sent to servers
As far as I can see the missing bits 3.2 needs to take that step are:
- reject http-Upgrade requests from clients.
Henrik Nordstrom wrote:
lör 2009-09-12 klockan 23:36 +1200 skrev Amos Jeffries:
Updating the checklist today I again wonder if we can repeat the step
from 2.7 and enable HTTP/1.1 on requests sent to servers
The default in 2.7 is 1.0 still. There is an option to enable 1.1, or
actually three..
Updating the checklist today I again wonder if we can repeat the step
from 2.7 and enable HTTP/1.1 on requests sent to servers
As far as I can see the missing bits 3.2 needs to take that step are:
- reject http-Upgrade requests from clients.
- reject Expect-100 requests from clients.
lör 2009-09-12 klockan 23:36 +1200 skrev Amos Jeffries:
Updating the checklist today I again wonder if we can repeat the step
from 2.7 and enable HTTP/1.1 on requests sent to servers
The default in 2.7 is 1.0 still. There is an option to enable 1.1, or
actually three.. (http11 cache_peer
12 matches
Mail list logo
