Skip to content

Commit a2b5c1f

Browse files
authored
Correct typos and grammatical mistakes in the HTTP headers cheat sheet (#1831)
1 parent 2242b11 commit a2b5c1f

File tree

1 file changed

+6
-6
lines changed

1 file changed

+6
-6
lines changed

cheatsheets/HTTP_Headers_Cheat_Sheet.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -95,7 +95,7 @@ The HTTP `Strict-Transport-Security` response header (often abbreviated as HSTS)
9595
9696
- *NOTE*: Read carefully how this header works before using it. If the HSTS header is misconfigured or if there is a problem with the SSL/TLS certificate being used, legitimate users might be unable to access the website. For example, if the HSTS header is set to a very long duration and the SSL/TLS certificate expires or is revoked, legitimate users might be unable to access the website until the HSTS header duration has expired.
9797

98-
Please checkout [HTTP Strict Transport Security Cheat Sheet](HTTP_Strict_Transport_Security_Cheat_Sheet.md) for more information.
98+
Please check out [HTTP Strict Transport Security Cheat Sheet](HTTP_Strict_Transport_Security_Cheat_Sheet.md) for more information.
9999

100100
### Expect-CT ❌
101101

@@ -107,7 +107,7 @@ Do not use it. Mozilla [recommends](https://developer.mozilla.org/en-US/docs/Web
107107

108108
### Content-Security-Policy (CSP)
109109

110-
Content Security Policy (CSP) is a security feature that is used to specify the origin of content that is allowed to be loaded on a website or in a web applications. It is an added layer of security that helps to detect and mitigate certain types of attacks, including Cross-Site Scripting (XSS) and data injection attacks. These attacks are used for everything from data theft to site defacement to distribution of malware.
110+
Content Security Policy (CSP) is a security feature that is used to specify the origin of content that is allowed to be loaded on a website or in a web application. It is an added layer of security that helps to detect and mitigate certain types of attacks, including Cross-Site Scripting (XSS) and data injection attacks. These attacks are used for everything from data theft to site defacement to distribution of malware.
111111

112112
- *NOTE*: This header is relevant to be applied in pages which can load and interpret scripts and code, but might be meaningless in the response of a REST API that returns content that is not going to be rendered.
113113

@@ -123,7 +123,7 @@ The `Access-Control-Allow-Origin` is a CORS (cross-origin resource sharing) head
123123

124124
#### Recommendation
125125

126-
If you use it, set specific [origins](https://developer.mozilla.org/en-US/docs/Glossary/Origin) instead of `*`. Checkout [Access-Control-Allow-Origin](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Access-Control-Allow-Origin) for details.
126+
If you use it, set specific [origins](https://developer.mozilla.org/en-US/docs/Glossary/Origin) instead of `*`. Check out [Access-Control-Allow-Origin](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Access-Control-Allow-Origin) for details.
127127
> `Access-Control-Allow-Origin: https://yoursite.com`
128128
129129
- *NOTE*: The use of '\*' might be necessary depending on your needs. For example, for a public API that should be accessible from any origin, it might be necessary to allow '\*'.
@@ -136,7 +136,7 @@ This header works together with Cross-Origin-Embedder-Policy (COEP) and Cross-Or
136136

137137
This mechanism protects against attacks like Spectre which can cross the security boundary established by Same Origin Policy (SOP) for resources in the same browsing context group.
138138

139-
As this headers are very related to browsers, it may not make sense to be applied to REST APIs or clients that are not browsers.
139+
As these headers are very related to browsers, it may not make sense to be applied to REST APIs or clients that are not browsers.
140140

141141
#### Recommendation
142142

@@ -250,7 +250,7 @@ If you do not control links on your website, you might want to set `off` as a va
250250

251251
> `X-DNS-Prefetch-Control: off`
252252
253-
- *NOTE*: Do not rely in this functionality for anything production sensitive: it is not standard or fully supported and implementation may vary among browsers.
253+
- *NOTE*: Do not rely on this functionality for anything production sensitive: it is not standard or fully supported and implementation may vary among browsers.
254254

255255
### Public-Key-Pins (HPKP)
256256

@@ -314,7 +314,7 @@ add_header "X-Frame-Options" "DENY" always;
314314

315315
### Express
316316

317-
You can use [helmet](https://www.npmjs.com/package/helmet) to setup HTTP headers in Express. The code below is sample for adding the `X-Frame-Options` header.
317+
You can use [helmet](https://www.npmjs.com/package/helmet) to setup HTTP headers in Express. The code below is a sample for adding the `X-Frame-Options` header.
318318

319319
```javascript
320320
const helmet = require('helmet');

0 commit comments

Comments
 (0)