camo

https://github.com/atmos/camo I think this is pretty well known? It's a good idea too for GitHub to protect it's users.

GitHub uses Camo [1] to serve assets like images and SVG files. It removes any "dangerous" code like JS from the file before serving it from a GitHub CDN. 1. https://github.com/atmos/camo

They just proxy it on the fly with camo: https://github.com/atmos/camo

I'm not sure if WordPress is actually doing this, but they might be using something like camo[1] to transparently rewrite any http:// URLs to an image proxy running on SSL. This gets harder to implement correctly depending on what kind of content you allow on your sites (i.e. does your CMS only permit sanitized HTML, or are users allowed to do basically anything?), so it's not a perfect solution for everyone, but it might work here. [1]: https://github.com/atmos/camo

Github's proxy[1] respects Cache-Control headers, so it will just pass through since we use Etags and Cache-Control: no-cache. [1]https://github.com/atmos/camo

Yeah Github's proxy [1] respects Cache-Control headers, so it will just pass through. [1]https://github.com/atmos/camo

SVG is in some way an advanced, editable version of PostScript, PDF's ancestor. Any SVG inside of an <img> tag is as safe as any image format. The JS code won't run, any external resources linked to from inside the SVG won't be loaded, the :visited CSS style is disabled[1]… For added security, you can even send an HTTP tag called Content-Security-Policy: default-src 'none'; img-src data:; style-src 'unsafe-inline' gives good results. That's what GitHub uses, by the way[2]. > It's not a format that's optimized for rendering like jpg You could argue the same of jpg in a comparison between jpg and bmp. You can animate SVGs even within an <img> tag with SMIL or CSS. Sure, there are a lot of features, and you could argue that it makes SVG complex; but the SVG specification[3] is not that much bigger than the PNG specification[4], if at all. It

Now it's your turn, Tumblr! It can't be that hard to obtain a wildcard certificate and enable SSL on Tumblr. If there is any remote content that might not work with SSL, either inform your users about it, or use an SSL proxy like GitHub's [0]. 0: https://github.com/atmos/camo

We proxy all external URL's through: https://github.com/atmos/camo

Github proxies the images in comments: https://github.com/blog/743-sidejack-prevention-phase-3-ssl-... Here's the code behind it: https://github.com/atmos/camo

FYI, Camo might be useful for this: https://github.com/atmos/camo There's also a Go (golang) port: https://github.com/cactus/go-camo I'm currently using go-camo in my own feed reader and have experienced some flakiness (images fail to load sometimes). (Also, nice work!)

To anyone now panicing about user generated content and non-SSL images, and thinking "What I need is some kind of SSL proxy for user generated images"... Node based SSL proxy: https://github.com/atmos/camo And I whipped one up in PHP for some old PHP site that I worked on if anyone wants to see that. I shoved that behind Nginx so that I also get a file cache for the most requested files. For my project I purchased an extra SSL domain name ( https://sslcache.se ), as I had some concern about serving user generated content on my primary domain. Concerns which are valid, as github.com recently acknowledged by moving their UGC pages to github.io .

Ah, but then PayPal IPN callbacks would get through, but the users would still get broken pages. Or are you suggesting bypassing CloudFlare for all dynamic content? In which case, why use them? I actually did use them just for a CDN for a few more days. I use a second domain (sslcache.se) to proxy inline images in user generated content that doesn't originate from an SSL site but the user is viewing my site over SSL. Similar to this https://github.com/atmos/camo , except mine isn't written in node.js Even then, users complained of broken images when they were logged in (on SSL). The very basic thing: CloudFlare fails silently, sometimes. Well, that still happened with very basic content. From CloudFlares perspective the sslcache.se service was a site of static files, as I prime the content (download in the background) when a user submits

Ah right: https://github.com/atmos/camo