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

2010-08-16 Thread noc
See Changes: [Automatic source maintenance ] SourceFormat Enforcement [Francesco Chemolli ] Fixed autoconf-refactor bug: improper handling of default /etc/hosts -- [...truncated 3450

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

2010-08-16 Thread noc
See Changes: [Automatic source maintenance ] SourceFormat Enforcement [Francesco Chemolli ] Fixed autoconf-refactor bug: improper handling of default /etc/hosts -- [...truncated 110

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

2010-08-16 Thread noc
See Changes: [Francesco Chemolli ] Fixed autoconf-refactor bug: improper handling of default /etc/hosts [Francesco Chemolli ] Moved stubs for calls in main.cc to a specific stub-file. --

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

2010-08-16 Thread noc
See Changes: [Francesco Chemolli ] Fixed autoconf-refactor bug: improper handling of default /etc/hosts [Francesco Chemolli ] Moved stubs for calls in main.cc to a specific stub-file. --

Hudson build is back to normal: 3.HEAD-i386-Debian-sid #346

2010-08-16 Thread noc
See

Re: 1xx response forwarding

2010-08-16 Thread Amos Jeffries
On Mon, 16 Aug 2010 15:53:42 -0600, Alex Rousskov wrote: > Hello, > > We need to forward 1xx control messages from servers to clients. I > see two implementation options: > > 1. Use Store. Squid client side expects responses via storeClientCopy, > so we will be using the usual/normal code

1xx response forwarding

2010-08-16 Thread Alex Rousskov
Hello, We need to forward 1xx control messages from servers to clients. I see two implementation options: 1. Use Store. Squid client side expects responses via storeClientCopy, so we will be using the usual/normal code paths. Multiple 1xx responses may be handled with relative ease. The

Re: HTTP/1.1 to clients in v3.2

2010-08-16 Thread Henrik Nordström
mån 2010-08-16 klockan 14:08 -0600 skrev Alex Rousskov: > Should we try implement what you described then? In summary: > >- If the next hop is known to be 1.1, send a chunked request. >- Otherwise, try to accumulate the full body, with a timeout. > Send 411 if we timed out while accu

Re: HTTP/1.1 to clients in v3.2

2010-08-16 Thread Alex Rousskov
On 08/16/2010 01:52 PM, Henrik Nordström wrote: mån 2010-08-16 klockan 13:30 -0600 skrev Alex Rousskov: Since Squid is a program and not a human being, we do need to hard-code a single default. Clearly, there will be ACLs to change the behavior, but if no options apply, we still need to do some

Re: HTTP/1.1 to clients in v3.2

2010-08-16 Thread Henrik Nordström
mån 2010-08-16 klockan 13:30 -0600 skrev Alex Rousskov: > Since Squid is a program and not a human being, we do need to hard-code > a single default. Clearly, there will be ACLs to change the behavior, > but if no options apply, we still need to do something. > > Yu have more-or-less said "no"

Re: HTTP/1.1 to clients in v3.2

2010-08-16 Thread Alex Rousskov
On 08/16/2010 01:17 PM, Henrik Nordström wrote: mån 2010-08-16 klockan 11:43 -0600 skrev Alex Rousskov: I am revisiting this issue in hope to enable HTTP/1.1 to clients. If Squid properly dechunks requests on the client side, what should happen to that dechunked request on the server side? Let'

Re: HTTP/1.1 to clients in v3.2

2010-08-16 Thread Henrik Nordström
mån 2010-08-16 klockan 11:43 -0600 skrev Alex Rousskov: > I am revisiting this issue in hope to enable HTTP/1.1 to clients. If > Squid properly dechunks requests on the client side, what should happen > to that dechunked request on the server side? Let's start with the most > general case were

Hudson build is back to normal: 3.HEAD-i386-OpenBSD-4.5 #503

2010-08-16 Thread noc
See

HTTP/1.1 to clients in v3.2

2010-08-16 Thread Alex Rousskov
On 05/01/2010 09:34 PM, Henrik Nordström wrote: I am not very comfortable with enabling 1.1 by default towards clients until - 1xx can be handled& signalled properly - server version cache implemented, enabling us to gett rid of most 411& 417 cases - forwarding of chunked requests

Hudson build is back to normal: 3.HEAD-amd64-FreeBSD-7.2 #522

2010-08-16 Thread noc
See

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

2010-08-16 Thread noc
See Changes: [Francesco Chemolli ] Moved stubs for calls in main.cc to a specific stub-file. [Amos Jeffries ] Author: Various Translators Translations Update auto-save [Amos Jeffries ] Fix missing include for rotate_logs

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

2010-08-16 Thread noc
See Changes: [Francesco Chemolli ] Moved stubs for calls in main.cc to a specific stub-file. [Amos Jeffries ] Author: Various Translators Translations Update auto-save [Amos Jeffries ] Fix missing include for rotate_logs

Hudson build is back to normal: 3.HEAD-amd64-CentOS-5.3 #751

2010-08-16 Thread noc
See

Re: Note about auth refcounting state / ntlm in trunk

2010-08-16 Thread Henrik Nordström
mån 2010-08-16 klockan 21:32 +1200 skrev Amos Jeffries: > I don't think thats making them scheme-specific as such. The child > classes inheriting from AuthUser will be doing that part. It does. Each instance of AuthUser is scheme specific, and because of this the related acls break down when mor

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

2010-08-16 Thread noc
See Changes: [Amos Jeffries ] dist missing files in kerberos helper [Automatic source maintenance ] SourceFormat Enforcement -- [...truncated 4535 lines...] ranlib libBlocking.a rm -f

Re: Note about auth refcounting state / ntlm in trunk

2010-08-16 Thread Amos Jeffries
Henrik Nordström wrote: mån 2010-08-16 klockan 18:15 +1200 skrev Amos Jeffries: So.. the difference being that you are suggesting the credentials text and parsing should be done on AuthUserRequest and no AuthUser should exist associated with it until fully authed? AuthUser only created/

Re: Patch for squidclient

2010-08-16 Thread Amos Jeffries
+1. Looks right to me now. Amos -- Please be using Current Stable Squid 2.7.STABLE9 or 3.1.6 Beta testers wanted for 3.2.0.1

Re: Note about auth refcounting state / ntlm in trunk

2010-08-16 Thread Henrik Nordström
mån 2010-08-16 klockan 18:15 +1200 skrev Amos Jeffries: > So.. the difference being that you are suggesting the credentials > text and parsing should be done on AuthUserRequest and no AuthUser > should exist associated with it until fully authed? > AuthUser only created/looked up at the po

Re: Patch for squidclient

2010-08-16 Thread Markus Moeller
(buf+len, BUFFER_SIZE-len, "%s" Thank you Amos -- Please be using Current Stable Squid 2.7.STABLE9 or 3.1.6 Beta testers wanted for 3.2.0.1 Markus squid-3-head-tools-20100816.diff Description: Binary data