Re: /bzr/squid3/trunk/ r9766: Bug 2674: Remove limit on HTTP headers read.

On 06/26/2009 01:02 AM, Amos Jeffries wrote: revno: 9766 committer: Amos Jeffries squ...@treenet.co.nz branch nick: 3.HEAD timestamp: Fri 2009-06-26 19:02:45 +1200 message: Bug 2674: Remove limit on HTTP headers read.

Re: [squid-users] NONE/411 Length Required

On 06/17/2009 12:00 AM, Mark Nottingham wrote: [ moving to squid-dev ] From what I can see, the site is using JavaScript to do autocomplete on a search field. The autocomplete requests use POST, but without a body. With Firefox, this results in a POST request without a body; i.e., it

Re: A little help with cbdata and requestLink

On 06/16/2009 09:57 PM, Mark Nottingham wrote: Thanks. Anybody else have a second to look? Please s/fwdStartFoo/fwdContinue/ and document what it is. Since this is Squid2 you do not have to do it, of course. Your cbdata and request manipulations appear technically correct to me. IMHO, the

[RFC] Breaking forwarding loops in transparent proxies

Hello, Squid detects forwarding loops in most configurations, but breaks them (using a customizable HTTP_FORBIDDEN response) only when working as an accelerator. Squid does not break loops when working as a transparent proxy. Interestingly enough, the breaking code comment (in the patch

[PATCH] Truncate HTTP response bodies to match clen

Truncate too-long HTTP response bodies to match their Content-Length header. Sometimes a broken server sends more than Content-Length bytes in the response. For example, a 302 redirect message with Content-Length: 0 header may include an HTML body. Squid used to send everything it read to the

Re: [PATCH] Truncate HTTP response bodies to match clen

Bundle Buggy has detected this merge request. For details, see: http://bundlebuggy.aaronbentley.com/project/squid/request/%3C4A450DFE.6040604%40measurement-factory.com%3E Project: Squid

Re: Problem with cached entries w/ETag and request without If-None-Match header

On 06/16/2009 08:13 AM, Jason Noble wrote: You're right, looks like I read that section too quickly. After reading the RFC more carefully, it appears that the case I'm having issues with is undefined. The closest thing I can find is 13.3.4: An HTTP/1.1 caching proxy, upon receiving a

Re: about https support for transparent proxy

On 06/13/2009 04:35 PM, Mikio Kishi wrote: Many people want https support for transparent proxy using tproxy. Now, squid is not supported. Certainly, https support may make security problem, but I think it's useful as an optional extra. As a trial, I implemented the patch for https support,

Re: [PATCH] Enhanced access logging, added ICAP logging, chunked requests, bug #2495 fix.

Bundle Buggy has detected this merge request. For details, see: http://bundlebuggy.aaronbentley.com/project/squid/request/%3C4A454B50.9030504%40measurement-factory.com%3E Project: Squid

Re: [PATCH] Enhanced access logging, added ICAP logging, chunked requests, bug #2495 fix.

On 06/26/2009 04:27 PM, Alex Rousskov wrote: Enhanced access logging, added ICAP logging, chunked requests, bug #2495 fix: Ported features accumulated on 3p0-plus branch as of r8937: - A hack to support chunked requests (see chunked_request_body_max_size in squid.conf). -

[PATCH] ICAP service chains and sets

Hello, Please consider the following changes for Squid3 trunk inclusion. They have been been tested in the lab and will be put in production. The ICAP chains feature (i.e., a pipeline of ICAP services) has been on many wish lists. ICAP service sets allow for backup ICAP servers which are

Re: [PATCH] ICAP service chains and sets

Bundle Buggy has detected this merge request. For details, see: http://bundlebuggy.aaronbentley.com/project/squid/request/%3C4A455F93.800%40measurement-factory.com%3E Project: Squid

Re: /bzr/squid3/trunk/ r9766: Bug 2674: Remove limit on HTTP headers read.

Alex Rousskov wrote: On 06/26/2009 01:02 AM, Amos Jeffries wrote: revno: 9766 committer: Amos Jeffries squ...@treenet.co.nz branch nick: 3.HEAD timestamp: Fri 2009-06-26 19:02:45 +1200 message: Bug 2674: Remove limit on HTTP headers

Re: [RFC] Breaking forwarding loops in transparent proxies

Alex Rousskov wrote: Hello, Squid detects forwarding loops in most configurations, but breaks them (using a customizable HTTP_FORBIDDEN response) only when working as an accelerator. Squid does not break loops when working as a transparent proxy. Interestingly enough, the breaking code

Re: /bzr/squid3/trunk/ r9766: Bug 2674: Remove limit on HTTP headers read.

Amos Jeffries wrote: Alex Rousskov wrote: On 06/26/2009 01:02 AM, Amos Jeffries wrote: revno: 9766 committer: Amos Jeffries squ...@treenet.co.nz branch nick: 3.HEAD timestamp: Fri 2009-06-26 19:02:45 +1200 message: Bug 2674: Remove