After configuring Squid to perform SSL Bump on HTTPS SSL requests from clients..i want to send this to another proxy that will perform its own MITM and connect to the 'target Server' and return back the information to the client........ What is needed for squid to pass the requests(after ssl bump is performed) to the second proxy?


box1 was updated with iptable rules

iptables -t nat -A OUTPUT -p tcp --dport 443 -j DNAT --to

box2 has SSL_BUMP configured to listen and decrypt on 8444.. however i am unsure how to configure squid how to pass the descrypted ssl redirect from the ssl_bump...I've tried cache_peer(parent) and squid does not successfully connect to the 'cache_peer(parent)..

  • What have you tried? What did you expect to happen? What happened instead? What does your config look like? Do you have any log entries from the times it didn't work as expected? – Jenny D Jun 2 '17 at 16:39
  • are you aware that this type of confirmation supported @JennyD ? – Jeryl Cook Jun 2 '17 at 17:08

I'm pretty sure you can't specify a downstream proxy server in squid.conf if you are using SslBump (or I couldn't when I used it with Squid 3.4.??). I'm guessing the way you could do this is set up another transparent https/SslBump iptables/squid as you have in your example:


with box4 redirecting all 443TCP traffic to box5 port 8884 (your https squid intercept port)

But do you really need to do this? Its looking over complicated to me.

BTW if you are using iptables (eg box2) as a router, you can run squid+ssl_bump on it too to save on boxes.

  • its called 'upstream'(forwarding to a cache_peer parent), not 'downstream' its possible with HTTP easily example: stackoverflow.com/questions/19199424/… in my case my squid is listening and ssl_bump on 8444..i have another proxy server(on 8440) configured as a cache_parent but its not working. – Jeryl Cook Jun 9 '17 at 18:01
  • 1
    Sorry, upstream yes. I found this on the squid forum from a couple fo years ago:Squid can: A) relay CONNECT message from client to any upstream proxy. B) generate CONNECT message on arriving intercepted HTTPS and relay that to upstream proxy IF (and only if) ssl_bump selects the 'splice' action. C) relay https:// URLs to an upstream TLS proxy. That is all at present. Squid cannot (yet) generate CONNECT messages to try and fetch TLS details via a non-TLS cache_peer. -- So does your setup fit B or C? – Jim ReesPotter Jun 13 '17 at 15:10

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.