<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class="">Hi guys,</div><div class="">can anyone suggest solution to make following scenario work using squid:</div><div class=""><br class=""></div><div class="">step1. </div><div class="">Client(actually server application) calls <a href="http://example" class="">HTTP://example</a>.org squid via proxy.</div><div class=""> |</div><div class="">V </div><div class="">step2. </div><div class="">Proxy(Squid) understands that all calls to <a href="http://example.org" class="">HTTP://example.org</a> should be changed to <a href="httpS://example.org" class="">HTTPS://example.org</a>, trusts CA that uses <a href="http://example.org" class="">example.org</a> and knows client certificate to use for https client authentication</div><div class=""><div class=""> |</div><div class="">V </div></div><div class="">step3.</div><div class="">Origin(some server in internet) accepts https request, authenticates client, returns response</div><div class=""><br class=""></div><div class="">The main aim is to make client know nothing about https complexity (storing certificates/keys, knowing specific algorithms etc), and make squid manage this things.</div><div class=""><br class=""></div><br class=""><div apple-content-edited="true" class="">
<span class="Apple-style-span" style="border-collapse: separate; border-spacing: 0px;"><div class="">Best regards,</div><div class="">Ilya Karpov</div><div class=""><a href="mailto:karpoftea@gmail.com" class="">karpoftea@gmail.com</a></div><div class=""><br class=""></div></span><br class="Apple-interchange-newline">
</div>
<br class=""></body></html>