So this port which is squid needs has to have connection with the client?or with itself? How will i do that? http_port 127.0.0.1:3128 ? would this work? -talha On Mon, Apr 23, 2012 at 4:03 PM, Amos Jeffries <squid3@xxxxxxxxxxxxx> wrote: > On 23/04/2012 9:07 p.m., Ahmed Talha Khan wrote: >> >> Hey, >> I am using 3.3 sources to make a transparent proxy. i have configured >> the http port in the squid like this >> >> >> http_port 192.168.8.40:3128 intercept ssl-bump >> generate-host-certificates=on dynamic_cert_mem_cache_size=4MB >> cert=/home/talha/squid/www.sample.com.pem >> key=/home/talha/squid/www.sample.com.pem >> >> But when i run squid i get these error at the start and my webpages >> wont open. I think these errors are the problem showing something in >> forwarding . >> >> 2012/04/23 16:06:44| ERROR: No forward-proxy ports configured. >> 2012/04/23 16:06:44| ERROR: No forward-proxy ports configured. >> 2012/04/23 16:06:44| ERROR: No forward-proxy ports configured. >> >> >> >> The above definition of http_port is exactly that of a forward-proxy >> port! isnt it? > > > No it is an interception port. Forward proxy port has no special mode > settings (intercept/tproxy/accel). > > >> So why is squid screaming about this? > > > Squid needs at least one port to serve the error page, FTP and gopher icons, > and other proxy-proxy communications from. Interception port mode now (3.2+) > has security checks which cause problems for that traffic. > > >> This runs in 3.1 >> btw. May be 3.2/3.3 have some changes. Running squid -k parse also >> shows no issue. Heres the relevant output of -k parse > > > Hmm. It should have. Thank you. > > Amos -- Regards, -Ahmed Talha Khan
