Re: [squid-users] Reverse proxy and URL filtering...

Gary Tai wrote:
> This is set up internally for proof of concept currently, so it
> doesn't have public access.
>

So does the same experiment in your browser bring up squid?
The point and advice remains unchnged.

Amos

>
>
> On Thu, Feb 28, 2008 at 9:04 AM, Amos Jeffries <squid3@treenet.co.nz> wrote:
>> Gary Tai wrote:
>> > I need to setup a reverse proxy on the same Windows server that allows
>> > only certain defined URLs (www.somedomain.com/Test/this_url_only.asp).
>> >
>> >
>> > Squid-Listen-On:8880 -> send to localhost:8888 (IIS)
>> >
>> > I've got the reverse proxy working using the following in my squid.conf file:
>> >
>> > http_port 192.168.10.81:8880 accel defaultsite=vmsquid01
>>
>> Typing "http://vmsquid01/" in my browser does not bring up your website.
>> That should be the FQDN for the site you are accelerating.
>>
>> You may also need "vhost".
>>
>>
>>
>> >
>> > cache_peer 127.0.0.1 parent 8888 0 no-query originserver
>> >
>> >
>> > I can't seem to get Squid to only allow defined URLs.
>> >
>> > Is this what I should be using?
>> >
>> > acl allowed_URL urlpath_regex ^Test/this_url_only.asp
>> >
>> > cache_peer_access 127.0.0.1 allow allowed_URL
>>
>> Is the regext case-sensative? You may need to add "urlpath_regex -i".
>>
>> So far so good.
>>
>> Amos
>> --
>> Please use Squid 2.6STABLE17+ or 3.0STABLE1+
>> There are serious security advisories out on all earlier releases.
>>

-- 
Please use Squid 2.6STABLE17+ or 3.0STABLE1+
There are serious security advisories out on all earlier releases.