-----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 ? I tried to input "http_port 80" below my reverse proxy configuration, but it seems that didn't work. - -- Linkwerk - Software und Beratung für vernetzte Information Telefon: +49 40 69 66 48 14 Web: www.linkwerk.com Linkwerk GmbH, Oberaltenallee 20a, 22081 Hamburg, Handelsregister Hamburg, HRB 95084 Geschäftsführer: Stefan Mintert -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkuGSRQACgkQSm4S1ty9BPXRZACgqIWhtfPgq/nZKNg5nqG3y8de lhgAnjU2EtSxEfmtjNXLtULLo2QKhlNr =wnj7 -----END PGP SIGNATURE-----