Consider closely what protocol you are sending to which Squid ports ...

# HTTP browser explicit proxy config
http_port 8080

# HTTP port 80 NAT'ed
http_port 3128 intercept ssl-bump
  generate-host-certificates=on
  dynamic_cert_mem_cache_size=4MB
  cert=cert.crt key=cert.key
  options=...

# HTTPS port 443 NAT'ed
https_port 3129 intercept ssl-bump
  generate-host-certificates=on
  dynamic_cert_mem_cache_size=4MB
  cert=cert.crt key=cert.key
  options=...

Once you understand what the protocols are it should be clear how and
why the config options work.

Amos

On 21/05/2014 11:31 p.m., vin_krish wrote:
> Hi Eliezer ,
> 
> I have configured as :
> 
> http_port 8080   //for forward proxy
> https_port 3128 intercept ssl-bump generate-host-certificates=on
> dynamic_cert_mem_cache_size=4MB cert=cert.crt key=cert.key options=
> https_port 3129 intercept ssl-bump generate-host-certificates=on
> dynamic_cert_mem_cache_size=4MB cert=cert.crt key=cert.key options=
> 
> but still 'protocol error' exists.
> 
> and I tried
> 
> http_port 8080   //for forward proxy
> http_port 3128 
> https_port 3129 intercept ssl-bump generate-host-certificates=on
> dynamic_cert_mem_cache_size=4MB cert=cert.crt key=cert.key options=
> 
> still the same 'protocol error'. 
> Is it due to the self-signed certificate......?
> It should work when I access http://www.hotmail.com, but it doesn't. As I'm
> redirecting port 80 to 3128.
> 
> Thanks for replying,
> 
> Regards,
> krish
> 
> 
> 
> --
> View this message in context: 
> http://squid-web-proxy-cache.1019090.n4.nabble.com/Hotmail-issue-in-squid-3-4-4-tp4666020p4666048.html
> Sent from the Squid - Users mailing list archive at Nabble.com.
> 

Reply via email to