Re: [squid-users] TCP_RESET non http requests on port 80

2016-09-05 Thread Omid Kosari
Filed a bug report http://bugs.squid-cache.org/show_bug.cgi?id=4585 -- View this message in context: http://squid-web-proxy-cache.1019090.n4.nabble.com/TCP-RESET-non-http-requests-on-port-80-tp4679102p4679361.html Sent from the Squid - Users mailing list archive at Nabble.com. _

Re: [squid-users] range_offset_limit not working as expected

2016-09-05 Thread sallo baloch
plz send me a squid.config file from https and http cahe On Mon, Sep 5, 2016 at 7:09 PM, Amos Jeffries wrote: > What are you expecting? > > The Squid native format access.log shows what was delivered to the > client, and what server was involved. It does not show how the > range_offset_limit dir

Re: [squid-users] Problems with Linux Worstations

2016-09-05 Thread Yuri Voinov
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 05.09.2016 22:25, Marcio Demetrio Bacci пишет: > Hi Amos > > Now, my squid.conf is as follow (very simple): > > START # > http_port 3128 > > debug_options 11,2 > > cache_mem 512 MB > cache_swap_low 80 > cache_swap_hig

Re: [squid-users] Problems with Linux Worstations

2016-09-05 Thread Marcio Demetrio Bacci
Hi Amos Now, my squid.conf is as follow (very simple): START # http_port 3128 debug_options 11,2 cache_mem 512 MB cache_swap_low 80 cache_swap_high 90 maximum_object_size 512 MB minimum_object_size 0 KB maximum_object_size_in_memory 4096 KB cache_replacement_poli

Re: [squid-users] reply_header_access Server deny (IF Server==squid)

2016-09-05 Thread Amos Jeffries
On 6/09/2016 1:39 a.m., Omid Kosari wrote: > Thanks but according to my other thread > http://squid-web-proxy-cache.1019090.n4.nabble.com/TCP-RESET-non-http-requests-on-port-80-td4679102.html > deny_info generates some other headers/footprints. > See Alex's last message in that thread. In particu

Re: [squid-users] range_offset_limit not working as expected

2016-09-05 Thread Amos Jeffries
What are you expecting? The Squid native format access.log shows what was delivered to the client, and what server was involved. It does not show how the range_offset_limit directive affected the server connection messages. The ORIGINAL_DST indicates that this is intercepted traffic. Notice how

[squid-users] range_offset_limit not working as expected

2016-09-05 Thread Omid Kosari
Hello, My config: acl download_until_end dstdomain .cdn.mozilla.net range_offset_limit none download_until_end Squid 3.5.19 1473082997.229697 x.29.186.47 TCP_MISS/206 300476 GET http://download.cdn.mozilla.net/pub/firefox/releases/48.0.2/update/win32/en-US/firefox-48.0.2.complete.mar - O

Re: [squid-users] reply_header_access Server deny (IF Server==squid)

2016-09-05 Thread Omid Kosari
Thanks but according to my other thread http://squid-web-proxy-cache.1019090.n4.nabble.com/TCP-RESET-non-http-requests-on-port-80-td4679102.html deny_info generates some other headers/footprints. -- View this message in context: http://squid-web-proxy-cache.1019090.n4.nabble.com/reply-header-ac

Re: [squid-users] More host header forgery pain with peek/splice

2016-09-05 Thread Amos Jeffries
On 5/09/2016 11:35 a.m., Marcus Kool wrote: > Thanks for your reply. > > The 13-year old child in me says "I want it fixed yesterday" > since false positives are very painful and cannot always > be prevented since the environment where Squid works is > not always that easy to control. > > You men