2 ms·
Not sure about <noscript_within> going all the way to the browser -- but it might be useful as a directive to a front-end reverse-proxy, working a little like a
by gojomo 16y ago
Not sure about <noscript_within> going all the way to the browser -- but it might be useful as a directive to a front-end reverse-proxy, working a little like an edge-side-include but telling it to strip stray SCRIPTs, that would provide a last line of defense against.
Not elegant, but perhaps by providing a separate independent layer of enforcement could prove worthwhile.
Still, there's the problem of having app developers rigorously declare the SCRIPT-suppressed regions. So perhaps instead the sense should be reversed: require app-designers to rigorously declare only those narrow areas where SCRIPTs are allowed -- with everything else stripped out (and logged as anomalous) by the bastion-proxy.