Difference between revisions of "HTTP headers"
Jump to navigation
Jump to search
↑ https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Content-Security-Policy
| (3 intermediate revisions by the same user not shown) | |||
| Line 14: | Line 14: | ||
* [[Permissions-Policy]] | * [[Permissions-Policy]] | ||
* <code>[[Cache-Control]]: [[no-cache]], [[no-store]], [[max-age]]</code> | * <code>[[Cache-Control]]: [[no-cache]], [[no-store]], [[max-age]]</code> | ||
| + | |||
| + | |||
| + | == Activities == | ||
| + | * Use [[Terraform aws lb: drop_invalid_header_fields]] to drop not valid headers | ||
== Related terms == | == Related terms == | ||
| Line 29: | Line 33: | ||
== See also == | == See also == | ||
| + | * {{HTTP headers}} | ||
* {{HTTP Header}} | * {{HTTP Header}} | ||
| − | |||
| − | |||
[[Category:Web]] | [[Category:Web]] | ||
Latest revision as of 15:15, 28 June 2024
WWW-AuthenticateAuthorization:Content-Security-Policy[1]X-Frame-Options(deprecated): https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/X-Frame-Options
strict-Transport-Security- Content-Security-Policy
- X-Frame-Options
- X-Content-Type-Options
- Referrer-Policy
- Permissions-Policy
Cache-Control: no-cache, no-store, max-age
Activities[edit]
- Use Terraform aws lb: drop_invalid_header_fields to drop not valid headers
Related terms[edit]
aws s3 cp --cache-control- Clickjacking
- Bearer token:
Authorization: Bearer .../... curl --header- Python,
urlliblibrary - HTTP Security headers
has been blocked by CORS policy no 'access-control-allow-origin' header is present on the request
Activities[edit]
- Read about Amazon CloudFront: https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/example-function-add-security-headers.html
- Cloudflare: https://developers.cloudflare.com/pages/how-to/add-custom-http-headers/
See also[edit]
- HTTP headers, Security headers, HTTP Security headers
- HTTP Headers:
Authorization:, X-Frame-Options, Content-Security-Policy, Cache-Control, Terraform:drop_invalid_header_fields
Advertising:
