Re: [squid-users] Hi, I am currenty trying out squid 3.0 in accel erator mode and have a few questions about redirecting url and url-paths. ..

Oh, thanx for the info. I have not tried squidguard but I have been
looking at it, seems the code has not been updated in ages.

Could you point me in the right direction about configuring the
redirects? As far as I have read about squidguard its purpose is
filtering urls when squid is used as a regular http proxy, is there any
difference in configuring it when using squid in accelerator mode?

/anders

Chris Perreault wrote:

>I've set up and use Squidguard from http://www.squidguard.org . I'm fairly
>new to squid, have been playing with it for about a month while juggling
>other tasks, but we want to do the same thing you are attempting. Squidguard
>let us set up exactly what you describe below. This wasn't difficult to do.
>We actually want to move to the point where we have two proxies set up in
>accelerated (reverse proxy mode) One for our users who are travelling and
>one for users at the office. This will let us present a single user
>experience for them. Domain.com/server1 will map to 192.x.x.1 and
>domain.com/server2 will map to 192.x.x.2 All they need to know is to go to
>the public site, www.domain.com and click on a link that brings them to this
>"portal" type page. This way they do not have to know a lot of different
>addresses. The above I get working fine with 2.5 stable5. Adding ldap will
>let us know who they are before they hit the menu page (portal) and then
>customers will see and have access to some links, inside people access to
>other links, etc.
>
>Chris Perreault
>Webmaster/MCSE
>The Wiremold Company
>West Hartford, CT 06010
>860-233-6251 ext 3426
>
>
>-----Original Message-----
>From: Anders Westerberg [mailto:anders.westerberg@molndal.se]
>Sent: Saturday, May 22, 2004 3:31 PM
>To: squid-users@squid-cache.org
>Subject: [squid-users] Hi, I am currenty trying out squid 3.0 in accelerator
>mode and have a few questions about redirecting url and url-paths...
>
>
>Hi, as the sub says, I am currenty trying out squid 3.0 in accelerator
>mode and have a few questions about redirecting url and url-paths...
>
>The setup im trying to achieve is using squid as a front end server for
>several back end servers. The optimal would be to have one url with
>url-paths for all the backend servers.
>
>This is the setup I am using today which works just fine.
>
>http_port xx.xx.xx.xx:80 vhost defaultsite=www.domain.com https_port
>xx.xx.xx.xx:443 cert=somecert.pem vhost
>defaultsite=webapp1.domain.com
>
>cache_peer 192.168.1.10 parent 80 0 originserver no-query no-digest
>proxy-only
>cache_peer 192.168.1.11 parent 80 0 originserver no-query no-digest
>proxy-only
>cache_peer 192.168.1.12 parent 80 0 originserver no-query no-digest
>proxy-only
>cache_peer 192.168.1.13 parent 80 0 originserver no-query no-digest
>proxy-only
>
>cache_peer_domain 192.168.1.10 www.domain.com domain.com www3.domain.com
>cache_peer_domain 192.168.1.11 webapp1.domain.com cache_peer_domain
>192.168.1.12 www2.domain.com cache_peer_domain 192.168.1.13
>webapp2.domain.com someapp.domain.com
>
>This works just fine but I have to have several different hostnames
>presented to the users. So if someone wants to access a special
>application on say webapp2.domain.com they would have to remember what
>server that application runs on, ie webapp1.molndal.se/app1, I would
>like to do something like this:
>
>webapp.domain.com/app1 redirects to webapp1.domain.com/app1
>webapp.domain.com/app2 redirects to webapp2.domain.com/app2
>webapp.domain.com/app3 redirects to webapp1.domain.com/app3
>
>I could set up a web site that listens on webapp.domain.com with all
>url-paths and redirect them with meta tags there but is seems like an
>ugly solution.
>
>Is this possible with squid 3.0 or do I have to use some kind of
>redirector software? It would have been sweet if I could just have used
>something like:
>
>cache_peer_domain 192.168.1.11 webapp1.domain.com webapp.domain.com/app1
>cache_peer_domain 192.168.1.13 webapp2.domain.com webapp.domain.com/app2
>
>But that does not work of course ;), it can never be easy.
>
>Any information would be appreciated.
>
>/anders
>
>
Received on Tue Jun 01 2004 - 13:01:35 MDT