3 ms·
It would be nice to have strong resource pinning. I've been in contract situations where coordinating with in-house IT for a new server deployment would have b
by carussell 9y ago
It would be nice to have strong resource pinning. I've been in contract situations where coordinating with in-house IT for a new server deployment would have been a massive, go-nowhere headache, while throwing a webapp together on my own and self-hosting would've been easy but a big problem wrt company policy on data export. Resource pinning solves this by bringing us into the realm of "auditable". Strong resource pinning would look something like this RFC, except the browser would refuse to accept new resource deployments without deliberate consent of the client. (Something that can be bypassed with a hard refresh, as in this RFC, is not strong enough.)
Other situations I imagine would benefit from this are web crypto and HIPAA compliance.
- pg_is_a_butt 9y agouh... how is "just trust the resources already on the client" more compliant than forcing known good resources to be included with every response? cache poisoning is specifically mentioned in the RFC as a major issue. this is terrible for web crypto and HIPAA compliance. you're all idiots