Re: [squid-users] squid 3.2.0.14 "request-too-large"
so i have tried couple of things but stil there is a problem: when accessing some pages i'm gettings this error: ERROR The requested URL could not be retrieved Invalid Request error was encountered while trying to process the request: GET /home/0,7340,L-8859-59304,00.html HTTP/1.1 Host: hot.ynet.co.il User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:9.0.1) Gecko/20100101 Firefox/9.0.1 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 Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7 Connection: keep-alive Referer: http://www.ynet.co.il/home/0,7340,L-8,00.html Cookie: __utma=1.296661974.1325193380.1325193380.1325193380.1; __utmb=1.1.10.1325193380; __utmc=1; __utmz=1.1325193380.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none) Some possible problems are: Request is too large. Content-Length missing for POST or PUT requests. Illegal character in hostname; underscores are not allowed. HTTP/1.1 "Expect:" feature is being asked from an HTTP/1.0 software. Your cache administrator is webmaster. Generated Thu, 29 Dec 2011 21:17:20 GMT by squid31012 (squid/3.2.0.14) it's a testing machine with ubuntu 11.10 squid 3.2.0.14 as a tproxy. building options: Squid Cache: Version 3.2.0.14 configure options: '--prefix=/opt/squid32014' '--includedir=/include' '--mandir=/share/man' '--infodir=/share/info' '--localstatedir=/opt/squid32014/var' '--disable-maintainer-mode' '--disable-dependency-tracking' '--disable-silent-rules' '--enable-inline' '--enable-async-io=8' '--enable-storeio=ufs,aufs' '--enable-removal-policies=lru,heap' '--enable-delay-pools' '--enable-cache-digests' '--enable-underscores' '--enable-icap-client' '--enable-follow-x-forwarded-for' '--enable-digest-auth-helpers=ldap,password' '--enable-negotiate-auth-helpers=squid_kerb_auth' '--enable-external-acl-helpers=ip_user,ldap_group,session,unix_group,wbinfo_group' '--enable-arp-acl' '--enable-esi--disable-translation' '--with-logdir=/opt/squid32014/var/log' '--with-pidfile=/var/run/squid32014.pid' '--with-filedescriptors=65536' '--with-large-files' '--with-default-user=proxy' '--enable-linux-netfilter' '--enable-ltdl-convenience' with the same options i built versions 3.2.0.5 till 3.2.0.14 my squid.conf file : # # Recommended minimum configuration: # # Example rule allowing access from your local networks. # Adapt to list your (internal) IP networks from where browsing # should be allowed acl ee src 192.168.0.0/16 acl localnet src 10.0.0.0/8 # RFC1918 possible internal network acl localnet src 172.16.0.0/12 # RFC1918 possible internal network acl localnet src 192.168.0.0/16 # RFC1918 possible internal network acl localnet src fc00::/7 # RFC 4193 local private network range acl localnet src fe80::/10 # RFC 4291 link-local (directly plugged) machines acl SSL_ports port 443 acl Safe_ports port 80 # http acl Safe_ports port 21 # ftp acl Safe_ports port 443 # https acl Safe_ports port 70 # gopher acl Safe_ports port 210 # wais acl Safe_ports port 1025-65535 # unregistered ports acl Safe_ports port 280 # http-mgmt acl Safe_ports port 488 # gss-http acl Safe_ports port 591 # filemaker acl Safe_ports port 777 # multiling http acl CONNECT method CONNECT # # Recommended minimum Access Permission configuration: # # Only allow cachemgr access from localhost http_access allow ee http_access allow localhost manager http_access deny manager # Deny requests to certain unsafe ports http_access deny !Safe_ports # Deny CONNECT to other than secure SSL ports http_access deny CONNECT !SSL_ports # We strongly recommend the following be uncommented to protect innocent # web applications running on the proxy server who think the only # one who can access services on "localhost" is a local user #http_access deny to_localhost # # INSERT YOUR OWN RULE(S) HERE TO ALLOW ACCESS FROM YOUR CLIENTS # # Example rule allowing access from your local networks. # Adapt localnet in the ACL section to list your (internal) IP networks # from where browsing should be allowed http_access allow localnet http_access allow localhost # And finally deny all other access to this proxy http_access deny all # Squid normally listens to port 3128 http_port 3129 tproxy http_port 3128 # Uncomment and adjust the following to add a disk cache directory. #cache_dir ufs /opt/squid32014/var/cache/squid 100 16 256 # Leave coredumps in the first cache dir coredump_dir /opt/squid32014/var/cache/squid # Add any of your own refresh_pattern entries above these. refresh_pattern ^ftp: 144020% 10080 refresh_pattern ^gopher:14400% 1440 refresh_pattern -i (/cgi-bin/|\?) 0 0% 0 refresh_pattern . 0 20% 4320 #end of squid.conf i compiled on the same machine 3.1.18 and it works fine. i will try lat
Re: [squid-users] squid 3.2.0.14 "request-too-large"
On 23/12/2011 16:28, Amos Jeffries wrote: On 24/12/2011 2:47 a.m., Eliezer Croitoru wrote: what im getting is: ERROR The requested URL could not be retrieved Invalid Request error was encountered while trying to process the request: Er, these are: "Invalid Request error was encountered..." With requests in origin server format. I will take a guess that these are status code 409 (Conflict)? In which case you will find security ALERT in cache.log and need to revaluate the interception and/or DNS setup carefully. i have used it as a direct forward proxy with no interception at all. i wil try it later and hope to soon again. Thank Eliezer Amos
Re: [squid-users] squid 3.2.0.14 "request-too-large"
On 24/12/2011 2:47 a.m., Eliezer Croitoru wrote: what im getting is: ERROR The requested URL could not be retrieved Invalid Request error was encountered while trying to process the request: Er, these are: "Invalid Request error was encountered..." With requests in origin server format. I will take a guess that these are status code 409 (Conflict)? In which case you will find security ALERT in cache.log and need to revaluate the interception and/or DNS setup carefully. Amos
Re: [squid-users] squid 3.2.0.14 "request-too-large"
what im getting is: ERROR The requested URL could not be retrieved Invalid Request error was encountered while trying to process the request: GET / HTTP/1.1 Host: facebook.com User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:9.0.1) Gecko/20100101 Firefox/9.0.1 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 Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7 Proxy-Connection: keep-alive Cookie: datr=6KKOTtGQTLeCfMvmitDZ4tXj; lu=RAkd5Kk1cX2qtayhUn9zBR8Q; p=1; c_user=1029903891; xs=60%3A66e234f1071c788d08062de6151741a3%3A0%3A1324408819; act=1324646317408%2F81%3A2; presence=EDvFA22A2EtimeF1324646317EstateFDutF1324646317862EvisF1EvctF0H0EblcF0EsndF1ODiFA21B00553145243A2CAcDiFA2223552591049184A2EyFA2gA2CQ1324646145EsF0CEchFDp_5f1029903891F11CEblF_7bCC Some possible problems are: Request is too large. Content-Length missing for POST or PUT requests. Illegal character in hostname; underscores are not allowed. HTTP/1.1 "Expect:" feature is being asked from an HTTP/1.0 software. Your cache administrator is webmaster. Generated Fri, 23 Dec 2011 13:42:05 GMT by c (squid/3.2.0.14) or ERROR The requested URL could not be retrieved Invalid Request error was encountered while trying to process the request: GET / HTTP/1.1 Host: www.yahoo.com User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:9.0.1) Gecko/20100101 Firefox/9.0.1 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 Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7 Proxy-Connection: keep-alive Cookie: B=fm82vh5797m2i&b=3&s=3o; fpc=d=IHP6TOQo94RKr1oKY.VClSUJRHXvm.gYtjAMfywGC2LLBqajEm8m_Vii7NRGTL6MgADNu0QhuhaPqq5ixWf0T0yKF162SJlg7X7PJODyVRKqEmuJ2n8Tb8RRFOZ8DuuLWlJ5y9H8wooXEg3h0HeEGk6E5rEKoBLlRXGp6yrzc3dYr_cg6Z72b8nCZ54HrWq5rl_Pi3E-&v=2; FPS=dl; CH=AgMNlQZ6NYZO7IsgACPoIAAmpSAAO58gAASrIAAmISAABvYgACXgIAAIUyAAKUkgADAX; BA=ba=2292&ip=79.181.17.57&t=1324486276 Pragma: no-cache Cache-Control: no-cache Some possible problems are: Request is too large. Content-Length missing for POST or PUT requests. Illegal character in hostname; underscores are not allowed. HTTP/1.1 "Expect:" feature is being asked from an HTTP/1.0 software. Your cache administrator is webmaster. Generated Fri, 23 Dec 2011 13:46:28 GMT by c (squid/3.2.0.14) hope to make it work somehow. Thanks Eliezer On 22/12/2011 2:35 p.m., Eliezer Croitoru wrote: On 22/12/2011 03:25, Amos Jeffries wrote: On 22/12/2011 1:13 p.m., Eliezer Croitoru wrote: updated to squid 3.2.0.14 and then i'm getting a page of "request-too-large" while trying to use facebook. so what i did after searching for anything like that in the past of squid to add reply_header_max_size 30 KB to the config and it works but squid is moving so slow so i switched back to 3.2.0.8. Thanks Eliezer Strange. You just *decreased* one of the size limits to make something "too big" get through. Other than the name of the error page being displayed, what are the status code and page contents describing situation? it will take me time to get the error back. deceased? what is the default limit? 64KB on headers, no limit on bodies. Amos
Re: [squid-users] squid 3.2.0.14 "request-too-large"
On 22/12/2011 2:35 p.m., Eliezer Croitoru wrote: On 22/12/2011 03:25, Amos Jeffries wrote: On 22/12/2011 1:13 p.m., Eliezer Croitoru wrote: updated to squid 3.2.0.14 and then i'm getting a page of "request-too-large" while trying to use facebook. so what i did after searching for anything like that in the past of squid to add reply_header_max_size 30 KB to the config and it works but squid is moving so slow so i switched back to 3.2.0.8. Thanks Eliezer Strange. You just *decreased* one of the size limits to make something "too big" get through. Other than the name of the error page being displayed, what are the status code and page contents describing situation? it will take me time to get the error back. deceased? what is the default limit? 64KB on headers, no limit on bodies. Amos
Re: [squid-users] squid 3.2.0.14 "request-too-large"
On 22/12/2011 03:25, Amos Jeffries wrote: On 22/12/2011 1:13 p.m., Eliezer Croitoru wrote: updated to squid 3.2.0.14 and then i'm getting a page of "request-too-large" while trying to use facebook. so what i did after searching for anything like that in the past of squid to add reply_header_max_size 30 KB to the config and it works but squid is moving so slow so i switched back to 3.2.0.8. Thanks Eliezer Strange. You just *decreased* one of the size limits to make something "too big" get through. Other than the name of the error page being displayed, what are the status code and page contents describing situation? it will take me time to get the error back. deceased? what is the default limit? Thanks ELiezer Amos
Re: [squid-users] squid 3.2.0.14 "request-too-large"
On 22/12/2011 1:13 p.m., Eliezer Croitoru wrote: updated to squid 3.2.0.14 and then i'm getting a page of "request-too-large" while trying to use facebook. so what i did after searching for anything like that in the past of squid to add reply_header_max_size 30 KB to the config and it works but squid is moving so slow so i switched back to 3.2.0.8. Thanks Eliezer Strange. You just *decreased* one of the size limits to make something "too big" get through. Other than the name of the error page being displayed, what are the status code and page contents describing situation? Amos
