[squid-users] squid 3.1.19 - error 22
Hi ! I’m using squid 3.1.19 with freebsd and when posting to some boards i get “error 22“ What may cause this ? It’s self compiled by the squid 3.1 port from the freebsd ports in x86 mode. I’m connecting directly to the internet, there is no further cache in between… When opening a second instance of the browser with the same uri and posting again the error is gone until the browser is closed ☹ Any ideas ? Regards, martin
[squid-users] FreeBSD squid 3.1.19 ZPH
Hi ! This might be a very stupid question, but perhaps i'm missing something: How can I enable TOS with squid 3.1.19 on freebsd ? I read I have to enable the ZPH patch or build it with --enable-zph-qos. How can I chose this in the options when doing a make ? Do I have to run ./configure --... before with freebsd, too ? (I'm asking this to this list because I read that squid is developed under freebsd...) And hints are greatly appreciated ;-) Regards, martin
[squid-users] Exchange WebServices
Hi ! Does anyone use Exchange-WebServices with squid ? We have it up and running with squid 3.1.19 under freebsd with the following config-options, but it takes very long to establish the first connection. When directly natting ews it's much faster. https_port xxx.xxx.xxx.xxx:443 accel cert=/usr/local/etc/squid/4f50b44b67bf9.crt key=/usr/local/etc/squid/4f50b44b67bf9.key defaultsite=g1.xxx.de cache_peer yyy.yyy.yyy.yyy parent 443 0 proxy-only no-query originserver login=PASS connection-auth=on ssl sslflags=DONT_VERIFY_PEER front-end-https=on name=OWA_HOST_pfs acl OWA_URI_pfs url_regex -i ^https:// g1. xxx.de/owa.*$ acl OWA_URI_pfs url_regex -i ^https:// g1. xxx.de/exchange.*$ acl OWA_URI_pfs url_regex -i ^https:// g1. xxx.de/public.*$ acl OWA_URI_pfs url_regex -i ^https:// g1. xxx.de/exchweb.*$ acl OWA_URI_pfs url_regex -i ^https:// g1. xxx.de/ecp.*$ acl OWA_URI_pfs url_regex -i ^https:// g1. xxx.de/OAB.*$ acl OWA_URI_pfs url_regex -i ^https:// g1. xxx.de/Microsoft-Server-ActiveSync.*$ acl OWA_URI_pfs url_regex -i ^https:// g1. xxx.de/rpc/rpcproxy.dll.*$ acl OWA_URI_pfs url_regex -i ^https:// g1. xxx.de/rpcwithcert/rpcproxy.dll.*$ ignore_expect_100 on acl OWA_URI_pfs url_regex -i ^https:// g1. xxx.de/EWS.*$ cache_peer_access OWA_HOST_pfs allow OWA_URI_pfs cache_peer_access OWA_HOST_pfs deny allsrc never_direct allow OWA_URI_pfs http_access allow OWA_URI_pfs in the access.log we get the following errors 1331048055.562 6 207.46.14.63 TCP_MISS/401 312 POST https://g1.xxx.de/EWS/Exchange.asmx - FIRST_UP_PARENT/OWA_HOST_pfs - 1331048055.929 6 207.46.14.63 TCP_MISS/401 705 POST https://g1.xxx.de/EWS/Exchange.asmx - FIRST_UP_PARENT/OWA_HOST_pfs - 1331048056.186 138 207.46.14.63 TCP_MISS/200 1422 POST https://g1.xxx.de/EWS/Exchange.asmx - PINNED/OWA_HOST_pfs text/xml Does anyone have any experiences or ideas ? Regards, martin
AW: [squid-users] Exchange WebServices
Hi, Amos ! ... ignore_expect_100 could be the reason. Exchange tries to use Expect:100-continue feature sometimes. Your browser may be timing out before it sends POST'd data. Without ignore_expect_100 we get 1331073616.344 0 207.46.14.62 NONE/417 4157 POST https://g1.xxx.de/EWS/Exchange.asmx - NONE/- text/html 1331073616.886 0 207.46.14.62 NONE/417 4157 POST https://g1.xxx.de/EWS/Exchange.asmx - NONE/- text/html 1331073659.207 0 207.46.14.62 NONE/417 4157 POST https://g1.xxx.de/EWS/Exchange.asmx - NONE/- text/html Excessive googling showed that it seems normal with EWS until now ;-) So as I have read it squid 3.2 will support the 1xx messages ? perhaps it gets better... Then we will have to wait for a freebsd port for 3.2 ;-) Although that said, the above POST look to be part of an NTLM handshake and only taking 150ms. Could you rate it ? I do not know if this fast, good, slow, bad or else ;-) Regards, martin
[squid-users] squid reverse-config - pass external clients ip as origin
Hi ! Is there somehow the possibility to tell squid in a reverse config to pass the external clients ip as the origin ip ? I know of the many x-forwarded-for discussions, but here I have a case with squid as a generic firewall package, where I cannot edit every internal destinations configs... Any help is greatly appreciated ;-) regards, martin
