Skip to content

Commit cbf992c

Browse files
Explain why using standard mechanisms is a good idea
Signed-off-by: David A. Wheeler <[email protected]>
1 parent 404dff3 commit cbf992c

File tree

1 file changed

+3
-0
lines changed

1 file changed

+3
-0
lines changed

secure_software_development_fundamentals.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -3694,6 +3694,9 @@ In 2017 it was found that 70% of tested sites
36943694
failed to correctly forbid browsers from storing cached content, because
36953695
they incorrectly used only the nonstandard request to store cached data
36963696
["Industry-wide Misunderstandings of HTTPS" by Independent Security Evaluators (ISE), July 12, 2017](https://www.ise.io/casestudies/industry-wide-misunderstandings-of-https/#5d).
3697+
You should always try to use a *standard* interface to request
3698+
a security-related capability where you can, to make it more likely that
3699+
the mechanism will work in the future.
36973700

36983701
You could also consider implementing extra double-checks to ensure that any cached data is only being sent to someone authorized to receive it.
36993702

0 commit comments

Comments
 (0)