On 05/18/2013 04:32 PM, Guy Helmer wrote:
further testing indicates that building with --enable_kqueue causes
squid not to read the remainder of the body
Yes, if my interpretation of the sources is correct, Squid kqueue code
does not fully support SSL yet :-(. There is no kqueue code to resume
On 05/18/2013 04:32 PM, Guy Helmer wrote:
Any thoughts on appropriate timeouts for the ICAP protocol? I have
not seen recommendations for timeouts in RFC 3507 or the ICAP
Errata.
Let the ICAP client determine them? :-)
Cheers,
Alex.
On May 17, 2013, at 7:25 PM, Alex Rousskov rouss...@measurement-factory.com
wrote:
On 05/15/2013 09:12 AM, Guy Helmer wrote:
I'm seeing something odd with icap REQMOD requests for HTTP POST
requests in Squid 3.3.4: the encapsulated body appears to not be
terminated by \r\n0\r\n. This
On 05/15/2013 09:12 AM, Guy Helmer wrote:
I'm seeing something odd with icap REQMOD requests for HTTP POST
requests in Squid 3.3.4: the encapsulated body appears to not be
terminated by \r\n0\r\n. This seems to occur consistently with bumped
SSL requests to graph.facebook.com:
The
I'm seeing something odd with icap REQMOD requests for HTTP POST requests in
Squid 3.3.4: the encapsulated body appears to not be terminated by \r\n0\r\n.
This seems to occur consistently with bumped SSL requests to graph.facebook.com:
19A7 52 45 51 4d 4f 44 20 69 63 61 70 3a 2f 2f 31 32
