Hi,
I am updating a url_rewrite helper. My helper is getting the following
input:
https://my.url/is/here - GET myip=10.0.0.1 myport=443
I've looked this up here
http://www.squid-cache.org/Versions/v3/3.5/cfgman/url_rewrite_extras.html
and found this:
Default Value: url_rewrite_extras "%>a/%>A
Hey never mind. I had the wrong idea by using deny_info.
I've got it working now.
Thanks for the help.
--
View this message in context:
http://squid-web-proxy-cache.1019090.n4.nabble.com/Squid-reverse-proxy-Redirect-based-on-http-header-tp4673063p4673083.html
Sent from the Squid - Users mailin
Hi,
I've managed to catch the requests with the following acl:
#
acl ios browser ^MYApp\/1\.3\.1
#
And I am able to redirect them were I want them with the following:
#
deny_info http://my.other.domain ios
http_reply_access deny ios
#
The requests are going through to the correct server, but the r
Hi Amos, thanks for the prompt reply.
So I could follow that example, but use this ACL instead:
acl aclname req_header header-name [-i] any\.regex\.here
# regex match against any of the known request headers. May be
# thought of as a superset of "browser", "referer" and "mime
That would be true, but we are using a wildcard certificate, and only
rewriting the subdomain, so the certificate is still valid.
Would squid 3.5 allow us to rewrite the subdomain in a similar way to your
redirect example, without relying on a helper script?
--
View this message in context:
ht
Hi Amos,
Thanks for the reply. It's weird that the <=2.4 operation still worked all
the time.
Anyway, I don't think what my helper is doing is exactly equivalent of that
because:
deny_info 301: https://api.domain.com%R site
is a redirect, which the client will be aware of. We want to continue
I tried to upgrade from squid 3.2.x to 3.5.x and found my url rewrite script
no longer works.
After trial and error, I found the latest version it works in is the latest
3.3.x so I've upgraded to this for now.
Here is my url_rewrite_program: http://pastebin.com/uaYUCkyY
I haven't been able to fig
Ah, working now. Thanks for fixing it.
--
View this message in context:
http://squid-web-proxy-cache.1019090.n4.nabble.com/Squid-mirror-ngtech-is-down-tp4668970p4668974.html
Sent from the Squid - Users mailing list archive at Nabble.com.
___
squid-
This squid mirror http://www1.ngtech.co.il/rpm/centos/6/SRPMS/ is down,
giving 404 errors.
Is there an alternate mirror for the pre-built squid binaries for CentOS6?
--
View this message in context:
http://squid-web-proxy-cache.1019090.n4.nabble.com/Squid-mirror-ngtech-is-down-tp4668969.html
