On Wed, 3 Mar 2004, Jon Kay wrote:
Because current browser implementations treat Content-Encoding much as
though it was Transfer-Encoding, we will implement Content-Encoding and
Accept-Encoding as though they were actually the Transfer-Encoding and
TE described in the HTTP specifications.
On Wed, 2004-03-03 at 20:39, Adrian Chadd wrote:
Hi,
coss, as it stands in squid-3, is completely unusable.
It bombs out because some of the callback data types aren't
actually cbdata allocated anymore.
Oh crap. I'm more and more tempted to import my IO rework, it works
there.
Rob
--
GPG
On Wed, Mar 03, 2004, Robert Collins wrote:
coss, as it stands in squid-3, is completely unusable.
It bombs out because some of the callback data types aren't
actually cbdata allocated anymore.
Oh crap. I'm more and more tempted to import my IO rework, it works
there.
Heh. Please. :)
Hi there,
I'm back with this task (again).
Jon: you are far more advanced than I am on understanding squid. I can start helping
content compression writing GzipCoder, if you want to.
(Already discussed) About TE/Transfer-Encoding vs Accept-Encoding/Content-Encoding:
Content-Encoding
hi,
I'm still having issues with squid-2.5 and delay pools.
The FDSET stuff is _very_ broken when you're using 1024 fds.
Here is a simple patch to 2.5 only which removes the whole
fdset thing.
I'd like to commit this so the delay pools stuff in 2.5
works for 1024 fds without _lots_ of messing
On Wed, 3 Mar 2004, Adrian Chadd wrote:
I'm still having issues with squid-2.5 and delay pools.
The FDSET stuff is _very_ broken when you're using 1024 fds.
More likely the way FD_SETSIZE is extended is broken for your libc
headers..
You need to remove far more fd_set references if this is
On Thu, Mar 04, 2004, Henrik Nordstrom wrote:
On Wed, 3 Mar 2004, Adrian Chadd wrote:
I'm still having issues with squid-2.5 and delay pools.
The FDSET stuff is _very_ broken when you're using 1024 fds.
More likely the way FD_SETSIZE is extended is broken for your libc
headers..
I
On Thu, Mar 04, 2004, Adrian Chadd wrote:
You need to remove far more fd_set references if this is the problem.
There is also seveal delay pool related fd_set usage in comm_poll, and a
few other places I think.
Ok. I must've missed them. Let me go through the codebase and remove
all
On Thu, 4 Mar 2004, Adrian Chadd wrote:
More likely the way FD_SETSIZE is extended is broken for your libc
headers..
I agree, but its becoming a pain to work around this.
Please verify the assert I sent. If it triggers we at least know this is
the problem.
Which libc are you using?
