[squid-users] http_port with "transparent" or "intercept"?

[Yuri Voinov]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
 
#       intercept    Support for IP-Layer NAT interception delivering
#            traffic to this Squid port.
#            NP: disables authentication on the port.

Squid tells you what's wrong:

 ERROR: No forward-proxy ports configured.


In addition with interception port you MUST define also forwarding port
(starting from 3.x AFAIK).

Better to you will be specify forwarding port 3128, by default (it uses
by cachemgr and other optional software), and some another, for example,
3127, as interception port.

17.04.16 22:21, Per Jessen пишет:
> I am in the process if migrating from 2.7 to 3.4, and have hit a minor
> problem -
> if I use "http_port 3128 transparent" as I did in 2.7, it works very
well,
> but I get a slew of errors on start-up:
>
> squid[1735]: ERROR: No forward-proxy ports configured.
> squid: Last message 'ERROR: No forward-pr' repeated 176 times,
suppressed by
> syslog-ng on sogo
>
> If I only specify "http_port 3128", browsers being redirected to squid
get
> this:
>
> <--------------
> The following error was encountered while trying to retrieve the URL:
>
/schools/gcsebitesize/science/add_aqa/photosynthesis/photosynthesisrev3.shtml
>
>     Invalid URL
>
> Some aspect of the requested URL is incorrect.
>
> Some possible problems are:
>
>     Missing or incorrect access protocol (should be "http://" or similar)
>
>     Missing hostname
>
>     Illegal double-escape in the URL-Path
>
>     Illegal character in hostname; underscores are not allowed.
>
> Your cache administrator is webmaster.
> ----------->
>
> I'm using squid-3.4.4 on openSUSE 13.2.  I have seen the 'intercept'
option,
> but it produces the same error messages.
>
>
> thanks
> Per Jessen, Zürich.
>
> _______________________________________________
> squid-users mailing list
> squid-users at lists.squid-cache.org
> http://lists.squid-cache.org/listinfo/squid-users

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
 
iQEcBAEBCAAGBQJXE7srAAoJENNXIZxhPexG6pcH/06SIdSg91HfbfjHBPjRJFak
5awblFidUpxm3u9gJbuX7DQ7BxPLUtcs+7ihF3uY0KhTS7QjcSoX7j3EU/EjDywi
0Tz4YZruPY/4oJj4lk1sB0wB/YBXmgG6DKE9IIB2ujosVtXVkoHG3hgRfqLUh4ZU
Cj7MrctsVyk4aelGFO2Nla9ukw2GoCa3ufzDFIKZuUqF0mWPLUqXSOi0tl7qC/K5
QLLoIsYHFKYfLiyXMYj1ag7N83i2Iry1ae97/4DJFBWyHEdmlYmh564eL0JVQzzZ
ed+P/OOR6VEHrnRgHoQf9cITdZPCxGxokFHY0KWLGRb5G/RyF1L5rq5E/8H5DyI=
=UPxo
-----END PGP SIGNATURE-----

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.squid-cache.org/pipermail/squid-users/attachments/20160417/6aa016f1/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0x613DEC46.asc
Type: application/pgp-keys
Size: 2437 bytes
Desc: not available
URL: <http://lists.squid-cache.org/pipermail/squid-users/attachments/20160417/6aa016f1/attachment.key>