Re: Build failed in Hudson: 3.HEAD-i386-FreeBSD-6.4 #444

On Thu, 19 Aug 2010 08:10:01 +0200, Kinkie wrote: > This is on west: > >> checking sasl/sasl.h usability... no >> checking sasl/sasl.h presence... no >> checking for sasl/sasl.h... no >> checking sasl.h usability... no >> checking sasl.h presence... no >> checking for sasl.h... no >> checking for

Re: Build failed in Hudson: 3.HEAD-i386-FreeBSD-6.4 #444

This is on west: > checking sasl/sasl.h usability... no > checking sasl/sasl.h presence... no > checking for sasl/sasl.h... no > checking sasl.h usability... no > checking sasl.h presence... no > checking for sasl.h... no > checking for sasl_errstring in -lsasl2... no > checking for sasl_errstring

Re: [PATCH] Compliance: rename Trailers header to Trailer everywhere.

On Wed, 18 Aug 2010 22:09:47 -0600, Alex Rousskov wrote: > Compliance: rename Trailers header to Trailer everywhere. > > RFC 2616 section 13.5.1 has a typo in Trailers header name. The correct > name is Trailer. See http://trac.tools.ietf.org/wg/httpbis/trac/ticket/9 > > Co-Advisor test cases:

[PATCH] Compliance: rename Trailers header to Trailer everywhere.

Compliance: rename Trailers header to Trailer everywhere. RFC 2616 section 13.5.1 has a typo in Trailers header name. The correct name is Trailer. See http://trac.tools.ietf.org/wg/httpbis/trac/ticket/9 Co-Advisor test cases: test_case/rfc2616/hopHdr-Trailer-toClt test_c

[PATCH] Compliance: remove Content-Length header if Transfer-Encoding is present

Compliance: remove Content-Length header if Transfer-Encoding is present. If after HTTP header parsing we have both "Transfer-Encoding: chunked" and Content-Length headers, remove the Content-Length entry. The adjusted behavior follows httpbis recommendations (ticket #95, part 2). The old cli

Build failed in Hudson: 3.HEAD-amd64-CentOS-5.3 #761

See Changes: [Amos Jeffries ] Bundle the purge and hexd tools with Squid sources. Fixes the remaining known errors with purge tool building within Squid source tree. This adds the auto-tools changes necessary to bundle the

Build failed in Hudson: 3.HEAD-i386-OpenBSD-4.5 #511

See -- Started by upstream project "3.HEAD-amd64-CentOS-5.3" build number 759 Building remotely on vobsd SCM check out aborted

Build failed in Hudson: 3.HEAD-amd64-CentOS-5.3 #760

See Changes: [Amos Jeffries ] Remove diff-reducer hack in rev10754 [Automatic source maintenance ] SourceFormat Enforcement -- Started by an SCM change Building on master [workspace]

Build failed in Hudson: 3.HEAD-i386-opensolaris #409

See Changes: [Automatic source maintenance ] SourceFormat Enforcement -- [...truncated 3448 lines...] /usr/sfw/lib/gcc/i386-pc-solaris2.11/3.4.3/../../../../include/c++/3.4.3/cwchar:17

Build failed in Hudson: 3.HEAD-i386-FreeBSD-6.4 #445

See Changes: [Automatic source maintenance ] SourceFormat Enforcement -- [...truncated 108 lines...] checking for /usr/bin/ld option to reload object files... -r checking for objdump..

Build failed in Hudson: 3.HEAD-i386-opensolaris #408

See Changes: [Automatic source maintenance ] SourceFormat Enforcement [Amos Jeffries ] Author: Alex Rousskov Bug 3016: HTTP/1.1 compliance: default keep-alive for 1.0/1.1 clients. aka. NTLM Authentication with Java UA + S

Build failed in Hudson: 3.HEAD-i386-FreeBSD-6.4 #444

See Changes: [Automatic source maintenance ] SourceFormat Enforcement [Amos Jeffries ] Author: Alex Rousskov Bug 3016: HTTP/1.1 compliance: default keep-alive for 1.0/1.1 clients. aka. NTLM Authentication with Java UA + S

Re: 1xx response forwarding

mån 2010-08-16 klockan 15:53 -0600 skrev Alex Rousskov: > Both approaches may have to deal with crazy offset management, > clientStreams manipulations, and other client-side mess. Yes. For now I think we need to bypass store to make this sane, and it's probably also a step in the right directio