thanks for your detailed reply, Amos.
now I have found out the culprit is large file descriptor number limit.
Docker CE for Debian package has set this limit (RLIMIT_NOFILE) in the
container to 1048576, thus squid set Squid_MaxFD to 1048576, then
allocates 1048576*392 = 392m memory for `fd_table`.
On 3/6/19 11:25 AM, George Xie wrote:
>> So disabling swap entirely on the server is not a great idea. It just
>> moves the error and shutdown to happen at peak traffic times when it is
>> least wanted.
> but I guess this is common in the "cloud" era, eg: Google Compute Engine.
Moreover, in many
Hi,
On Windows I'm getting an error returned when attempting to upload a file to an
Amazon AWS S3 bucket, using either the WinSCP app or just using the S3 upload
interface via browser, pointing to my squid proxy.I can download just fine, but
not upload. ECAP is enabled for both the request and t
On 3/6/19 1:00 PM, Russel McDonald wrote:
> I've indeed read a few forum links about just this issue, but confused
> as to whether chunking is supposed to finally work for 3.5.28
Chunked requests should be supported in all modern Squid versions,
including v3.5.28. There are some corner cases wher
hi,
after going trough rfc3507 (icap) im not really sure how a icap server
is supposed to work together with squid, for example the python icap
servers that are available via github have method names like:
example_OPTIONS, example_REQMOD, example_RESPMOD
yara_OPTIONS_, yara_
or the
On 3/6/19 3:33 PM, steven wrote:
> after going trough rfc3507 (icap) im not really sure how a icap server
> is supposed to work together with squid,
At the protocol level, an ICAP server works pretty much how RFC 3507
describes it. At the ICAP server software/application level, each server
"works