On 9/16/19 5:26 PM, Felipe Arturo Polanco wrote: > I have a RESPMOD icap server that supports Allow:206 in the OPTIONS > response. > Do you know why squid doesn't Allow 206 for files? Squid follows the ICAP 206 extension specs and does not send Allow:206 unless it can buffer the entire HTTP message. In your particular case, the "file" is 10000000 bytes long. That size probably exceeds Squid buffering ability (64KB IIRC). AFAICT, Squid also does not send Allow:206 for messages without bodies. Alex. P.S. Please note that Squid has no notion of "HTML", "archive", or "file". Squid does not understand MIME types and such. > RESPMOD icap://127.0.0.1:13440/example ICAP/1.0 > Host: 127.0.0.1:13440 <http://127.0.0.1:13440> > Date: Mon, 16 Sep 2019 20:51:00 GMT > Encapsulated: req-hdr=0, res-hdr=337, res-body=579 > Allow: trailers > X-Client-IP: 192.168.0.6 > > GET http://203.0.113.1/file.zip HTTP/1.1 > User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:69.0) > Gecko/20100101 Firefox/69.0 > Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8 > Accept-Language: en-US,en;q=0.5 > Accept-Encoding: gzip, deflate > DNT: 1 > Upgrade-Insecure-Requests: 1 > Host: 203.0.113.1 > > HTTP/1.1 200 OK > Date: Mon, 16 Sep 2019 20:51:00 GMT > Server: Apache/2.4.6 (CentOS) > Last-Modified: Thu, 29 Aug 2019 13:54:58 GMT > ETag: "989680-59141d9f0557a" > Accept-Ranges: bytes > Content-Length: 10000000 > Content-Type: application/zip > http://www.icap-forum.org/documents/specification/draft-icap-ext-partial-content-07.txt _______________________________________________ squid-users mailing list squid-users@xxxxxxxxxxxxxxxxxxxxx http://lists.squid-cache.org/listinfo/squid-users
