Re:How a banner ad for H&R Block appeared on Apple.com witho...
by tibbon on Monday April 08, 2013 @09:16AM
(#5511456)
What about for your server-side stuff? Like caching in Varnish?
[ Parent
| on HN ]
Re:How a banner ad for H&R Block appeared on Apple.com witho...
by halfasleep on Monday April 08, 2013 @10:37AM
(#5511921)
You can do the SSL before Varnish, then it makes no difference.
Re:How a banner ad for H&R Block appeared on Apple.com witho...
by jbooth on Monday April 08, 2013 @01:59PM
(#5513348)
Does that work? Each client has its own key, so your caching goes from "one cached copy for everyone" to "one cached copy per client", right? Or am I missing something there?
Re:How a banner ad for H&R Block appeared on Apple.com witho...
by cortesoft on Monday April 08, 2013 @02:28PM
(#5513544)
No, you could still have one cached copy for everyone. The SSL termination happens before the user's request gets to the caching server. As far as the cache is concerned, it is a regular http request. The only problem is you cannot have generic caches that live closer to the end user; the cache has to be controlled by the person controlling the SSL termination.
Re:How a banner ad for H&R Block appeared on Apple.com witho...
by jbooth on Monday April 08, 2013 @03:24PM
(#5513897)
So you're talking about caching the cleartext and then encrypting it for each client, which is totally doable.
I (possibly mis-) understood the original comment to be claiming that you could cache the ciphertext, to which I just wanted to make sure I wasn't missing some huge piece of understanding.
Re:How a banner ad for H&R Block appeared on Apple.com witho...
by X-Istence on Monday April 08, 2013 @03:38PM
(#5513991)
Varnish doesn't do HTTPS... so you have to put something that does SSL in front of varnish, which sits in front of your real web server:
SSL -> varnish -> backend varnish -> backend