Le mercredi 23 novembre 2011 à 23:37 +1300, Amos Jeffries a écrit : > De: > Amos Jeffries > <squid3@xxxxxxxxxxxxx> > À: > squid-users@xxxxxxxxxxxxxxx > Sujet: > Re: ERROR: No > forward-proxy ports configured > Date: > Wed, 23 Nov 2011 23:37:00 +1300 > (23/11/2011 11:37:00) > > > On 23/11/2011 11:14 p.m., David Touzeau wrote: > > Dear i'm using squid 3.2.0.13-20111121-r11422 > > for each request i receive an event > > > > Nov 23 11:08:24 kav4proxy64Coatpont squid[16844]: ERROR: No > > forward-proxy ports configured. > > Nov 23 11:08:24 kav4proxy64Coatpont squid[16844]: ERROR: No > > forward-proxy ports configured. > > Nov 23 11:08:24 kav4proxy64Coatpont squid[16844]: ERROR: No > > forward-proxy ports configured. > > Nov 23 11:08:24 kav4proxy64Coatpont squid[16844]: ERROR: No > > forward-proxy ports configured. > > > > > > here it is a piece of config file > > > <snip> > > > > #http/https ports > > http_port 33070 transparent > > > > So, only one port, and its a NAT traffic receiving port. Looks like > Squid was right, "no forward-proxy ports configured". > > Should not be on every request, that is a sign of some other problem > happening. Just on the ones which need to produce internal URLs (ie > error page icons, FTP directory icons, cache manager requests, etc). > Squid requires a forward-proxy port for the URL it tells the browser > to > fetch those icons from. A NAT or TROXY receiving port is somewhat > vulnerable to forgery attacks and Squid now avoids publishing its > details. Accel ports have some problematic cases in the parser and > until > those are figured out properly they are avoided as well. Which just > leaves the regular old forward-proxy port for now. > > Adding "http_port 3128" or somesuch is enough to avoid this message. > > Amos This fix the error, thanks !
