<html><body bgcolor="#FFFFFF"><div>I have nginx listening on port 443 , proxying the requests. The certificate can be easily setup with nginx.</div><div><br></div><div>It works flawlessly.<br><br>On Jun 17, 2011, at 8:28 AM, Lars Jørgensen <<a href="mailto:lajo@kb.dk">lajo@kb.dk</a>> wrote:<br><br></div><div></div><blockquote type="cite"><div>
<div class="Section1">
<p class="MsoNormal"><span lang="DA">Hi,<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="DA"><o:p> </o:p></span></p>
<p class="MsoNormal">We're building a varnish cache to put on a separate machine in front of a site that uses both http and https. Varnish is of course only supposed to cache http requests, but what is the best practice to pass https through to the backend?
I'm thinking about putting a separate varnish instance up on port 443 that does a pipe on all requests.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Lars<o:p></o:p></p>
</div>
</div></blockquote><blockquote type="cite"><div><span>_______________________________________________</span><br><span>varnish-misc mailing list</span><br><span><a href="mailto:varnish-misc@varnish-cache.org">varnish-misc@varnish-cache.org</a></span><br><span><a href="http://www.varnish-cache.org/lists/mailman/listinfo/varnish-misc">http://www.varnish-cache.org/lists/mailman/listinfo/varnish-misc</a></span></div></blockquote></body></html>