It would be somewhat hard. You couldn't do things like CSRF tokens or any kind o... | Hacker News

Hacker Newsnew | past | comments | ask | show | jobs | submit

		dham on Jan 30, 2016 \| parent \| context \| favorite \| on: Get HTTPS for free It would be somewhat hard. You couldn't do things like CSRF tokens or any kind of data that comes from the server and rendered on the page. Also the assets couldn't be named with hashes to be cached indefinitely. But the concept is interesting.

mintplant on Jan 30, 2016 [–]

> Also the assets couldn't be named with hashes to be cached indefinitely.

I don't see why not.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact