Search squid archive

Re: Squid reverse proxy and port mapping

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Mirabello Massimiliano wrote:
Hi all,

I have a problem I couldn't solve. I looked for documentation or
examples but a could not find (or I didn't uderstand) a solution.

I have an application that send http/https request on different ports of
my http server. What I need is to proxy a request received on a specific
port (e.g. 8080) on my frontend server (the one running squid) to a
specific port (e.g. 9080) of my backend server (eventually the same
server running squid). The same operation has to be executed for other
ports for the same backend server or eventually on a different one.

The following table should be more explicative.


Squid listening port		backend host	backend port
-----------------------------------------------------------------
8080					127.0.0.1		9080
8081					127.0.0.1		9081
8082					10.0.0.2		9082
8083					10.0.0.3		9080


There's anyone could provide an example to do this?
I use squid 3.0

ACL == myport / myip

acl port8080 myport 8080
cache_peer 120.0.0.1 parent 9080 0 name=local9080
cache_peer_access local9080 allow port8080 ...

acl port8081 myport 8081
cache_peer 120.0.0.1 parent 9081 0 name=local9081
cache_peer_access local9081 allow port8081 ...

etc, etc.

For my curiosity,
why the HTTP on different ports? squid can route internally using cache_peer_access and vhost. I can kind of understand the HTTPS, although singe multi-domain certificate is simpler.

Amos

[Index of Archives]     [Linux Audio Users]     [Samba]     [Big List of Linux Books]     [Linux USB]     [Yosemite News]

  Powered by Linux