[this should be on squid-dev instead]
On 02/09/2016 01:20 PM, Prashanth Prabhu wrote:
> Here's the behavior I have seen: When the connection is set up, the
> buffer gets a size of 16KB (default). Squid reads from the socket,
> parses the data, and then sends it towards c-icap as appropriate. Now,
On 02/13/2016 01:47 AM, Amos Jeffries wrote:
> On 11/02/2016 5:27 a.m., Alex Rousskov wrote:
>> On 02/10/2016 08:59 AM, Amos Jeffries wrote:
>>> This is the updated patch implementing RFC 3986 URI coding ('URL-escaping').
>>>
>>> So far all the audit suggestions except Tokenizer usage have been
>>>
On 02/12/2016 08:30 AM, Amos Jeffries wrote:
> On 12/02/2016 4:48 p.m., Alex Rousskov wrote:
>> On 02/11/2016 08:14 PM, Amos Jeffries wrote:
>>> On 12/02/2016 7:21 a.m., Alex Rousskov wrote:
On 02/11/2016 10:20 AM, Amos Jeffries wrote:
> One issue was uncovered during this:
>
This bug had unfortunately gotten lost in the flood. The bug reporters
proposed patch seems to be correct in terms of its intention.
This version of the patch adds the missing {} and uses fatalf() instead
of exit(). It also goes a little further and corrects the outstanding
errno handling issues i
[+ squid-dev; bcc ssquid-users]
Hi Alex,
Sorry about the late reply.
Please see inline.
>> Here's the behavior I have seen: When the connection is set up, the
>> buffer gets a size of 16KB (default). Squid reads from the socket,
>> parses the data, and then sends it towards c-icap as appropriat
