Re: [squid-users] SQUID proxy server configuration

yes you are right, i wrote the URL in a wrong way, it is like this way
: tomcat.no-ip.com:8000,
actually the whole story is not about let this accessible to public,
it will be just for development
purposes so it does not matter to use port 8000, where the other thing
that my ISP blocks the
port 80 to avoid giving the chance to set servers like am doing, so
thats why am using port 8000
for Squid and 80 for my web servers.

and Jakob thanks for help, but you forgot to guide me how the
configurations will look like :( ?

On Sun, May 3, 2009 at 10:29 PM, Jakob Curdes <jc_at_info-systems.de> wrote:
>
>>
>> - i have a machine that has Squid and apache servers both on same
>> machine, apache listens to port 80 where Squid listens to port 8000.
>> - another machine on the same network has IIS server listens to port 80.
>>
>> server (like tomcat.no-ip.com) over the internet i receive a response
>> from Squid telling that "the requested URL could not be retrieved"
>> followed by "access denied", so did configure Squid in the right way?
>>
>
> So you are accessing port 80 at tomcat.no-ip.com? Then you do not reach
> squid; you wrote yourself that your squid listens on port 8000. Either this
> is not true or the error message is coming from apache, not from squid. To
> make sense, your setup needs:
>
> - two IP addresses for squid
> - squid listening on port 80 for both addresses
> - two ip addresses for the web servers OR different ports (not 80) for the
> webservers where they are listening
> - squid forwarding rules for the squid addresses and port 80 to the
> webserver addresses and ports
> - and ACLs for squid that allow the traffic designated for the webservers.
>
> It looks to me you are trying to do it the other way round - putting a squid
> on port 8000 before a webserver on port 80.
> In this way you will end up with a publicly accessible webserver on port
> 8000 which is probably not what you want.
> Note that there is a fundamental difference  between the "normal" and
> "reverse" proxy situations; also one squid can handle both you really need
> to configure a squid reverse proxy with a public announced port whereas for
> an internal proxy can listen on an arbitrary port since the network is under
> your control!
>
>
> Hope this helps,
> Jakob Curdes
>

-- 
ubuntu
a.akkad