Bastian Spanneberg wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Amos Jeffries wrote:
Because the "accel" flag tells Squid to behave like th authoritative web
server for all incoming requests. When it needs auth it sends a web-server
auth challenge (linked to domain name by the browser to prevent XSS
credential loss). Not a proxy challenge (linked to the proxy IP or user
session by the browser).
To require a second http_port line without "accel" that browsers are
configured to connect to for regular proxy access.
Thx Amos
But judging from my tests, it doesn't work on the same port, right ?
What I would like to do is, that Squid serves one port and then
distinguishes between reverse proxy requests, and proxy requests.
Is this possible ?
No.
I tried to input "http_port 80" below my reverse proxy configuration,
but it seems that didn't work.
They need to be different port numbers. Sorry if that was not made clear
enough.
Regular proxy access on the standard proxy 3128 and web service on the
standard web server port 80 with accel etc.
Then firewall the regular proxy port away from the wide Internet.
Amos
--
Please be using
Current Stable Squid 2.7.STABLE7 or 3.0.STABLE24
Current Beta Squid 3.1.0.16
