On Mon, Jun 11, 2012 at 11:32 AM, Amos Jeffries <squid3@xxxxxxxxxxxxx> wrote: > On 11/06/2012 6:11 p.m., Muhammad Yousuf Khan wrote: >> >> On Sun, Jun 10, 2012 at 10:54 PM, Eliezer Croitoru<eliezer@xxxxxxxxxxxx> >> wrote: >>> >>> proxy is uses as a server to client that is aware of it. >>> this is what called forward proxy. >>> you define in the browserthe proxy address and port then use it. >>> to work with that you define in squid.conf the line: >>> http_port 3128 >>> or any other port. >>> if you want to "intercept" the clients connections so the proxy will >>> always >>> work on their traffic you must use another argument: >>> http_port 3128 intercept >> >> i just learn that "intercept" is a new name of "transparent" however i >> can not use transparent since i want to block https domains in working >> hours which is not possible in transparent. since squid is working >> only on http traffic. correct me if i am wrong since i am new? > > >>> some more info about it you can find here: >>> http://www.squid-cache.org/Doc/config/http_port/ >>> >>> are you using linux? >>> if so did you configure any iptables rules for squid to work? >> >> yes i am using linux. do you mean that i should redirect 3128 traffice >> to port 80 via iptables and squid will be listening on port 80. is >> this what you mean? > > > He was asking if you have "transparent interception proxy" setup. You said > no. sorry for my weak english. i understood it wrong. > > IE is apparently not working properly. When configured with a proxy it > should be passing HTTP to the proxy in proxy format. It is passing HTTP to > the proxy in a different format which is only safely used on port 80. > > In particular the format sent lacks the "http://"; part of URL and Squid is > unable to determine whether it is an HTTP, HTTPS, FTP, Gopher or some other > internal request. > you were right. restart of the system resolves the issue. i believe it was an application layer issue. it has nothing to do with squid. Thanks, > > Amos
