RE: Bug #1616: assertion failed:comm_generic.c:65:F-flags.openonstoreResumeFD.

tis 2006-06-27 klockan 08:16 +0800 skrev Steven Wilton: In the original code for 2.5, I had the following logic in commResumeFD() to handle this situation if(!(F-read_handler) || !(F-epoll_backoff)) { debug(5, 2) (commResumeFD: fd=%d ignoring read_handler=%p,

Re: squid-3 vs 2.6

tis 2006-06-27 klockan 08:22 +0800 skrev Adrian Chadd: Which reminds me, I should really spend some time making sensible defaults when COSS is using AUFS - right now the aiops code doesn't create any threads because n_aufs_dirs (or whatever it is) is set to 0; one has to override it by the

Re: Occasional Zero Sized Reply error with 2.6

tis 2006-06-27 klockan 10:25 +0200 skrev Guido Serassio: Could you set a breakpoint on the ERR_ZERO_SIZE_OBJECT fwdFail call in http.c httpReadReply, and print read_sz from there.. (non-optimized build please..) Obviously during a failed request ? Yes.. this code is only reached on such

Re: Occasional Zero Sized Reply error with 2.6

Hi, At 10.40 27/06/2006, Henrik Nordstrom wrote: tis 2006-06-27 klockan 10:25 +0200 skrev Guido Serassio: Could you set a breakpoint on the ERR_ZERO_SIZE_OBJECT fwdFail call in http.c httpReadReply, and print read_sz from there.. (non-optimized build please..) Obviously during a failed

Re: Occasional Zero Sized Reply error with 2.6

tis 2006-06-27 klockan 12:39 +0200 skrev Guido Serassio: Hi, At 10.40 27/06/2006, Henrik Nordstrom wrote: tis 2006-06-27 klockan 10:25 +0200 skrev Guido Serassio: Could you set a breakpoint on the ERR_ZERO_SIZE_OBJECT fwdFail call in http.c httpReadReply, and print read_sz from

Re: Occasional Zero Sized Reply error with 2.6

tis 2006-06-27 klockan 13:30 +0200 skrev Henrik Nordstrom: One question: Are you using NTLM/Negotiate proxy authentication? If you are then the problem should be fixed now. Regards Henrik signature.asc Description: Detta är en digitalt signerad meddelandedel

Re: Occasional Zero Sized Reply error with 2.6

lör 2006-06-24 klockan 08:48 +0800 skrev Adrian Chadd: I'm seeing it in my polygraph testing under 2.6 + COSS. It may be related. Most likely not... there was a nasty bug related to persistent connections and NTLM authentication.. Regards Henrik signature.asc Description: Detta är en

Open issues for 2.6

None critical / blocker for the release, but still 761: diskd unstable 1584: WCCPv2 unable to register with more than one router on Linux (IP ID IOS issue) 1602: Need to implement TCP fallback for DNS 1638: Connection pinning a bit too agressive. Should not pin due to local authentication,