certificates
Here are 665 public repositories matching this topic...
-
Updated
Sep 12, 2018 - HTML
-
Updated
Jun 30, 2022 - C#
-
Updated
Jul 5, 2022 - Python
-
Updated
Aug 11, 2021 - Python
-
Updated
Jun 21, 2022 - TypeScript
-
Updated
Dec 16, 2021
-
Updated
Jun 22, 2022 - C++
-
Updated
May 22, 2022 - Go
-
Updated
Jul 6, 2022 - Python
-
Updated
Jul 5, 2022 - Go
-
Updated
Jul 1, 2022 - Go
-
Updated
Nov 21, 2021 - PHP
-
Updated
Oct 11, 2020 - Python
-
Updated
May 18, 2020 - Shell
-
Updated
Feb 16, 2022 - Go
-
Updated
Feb 17, 2022 - Go
-
Updated
Jul 4, 2022 - Go
-
Updated
Jun 20, 2022
-
Updated
May 5, 2022 - Shell
-
Updated
Apr 15, 2017 - Go
-
Updated
Sep 17, 2020 - Go
-
Updated
Jul 16, 2021 - JavaScript
-
Updated
Dec 14, 2021 - Shell
-
Updated
May 21, 2022 - Rust
-
Updated
Jun 2, 2022 - Go
-
Updated
May 18, 2021 - Go
-
Updated
Jun 24, 2022 - Java
Improve this page
Add a description, image, and links to the certificates topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the certificates topic, visit your repo's landing page and select "manage topics."

Formed in 2009, the Archive Team (not to be confused with the archive.org Archive-It Team) is a rogue archivist collective dedicated to saving copies of rapidly dying or deleted websites for the sake of history and digital heritage. The group is 100% composed of volunteers and interested parties, and has expanded into a large amount of related projects for saving online and digital history.

The recommendation is to set
Cache-Control: private, no-storeon any endpoint with sensitive information. Because while you can protect the traffic with TLS, you also need to keep sensitive information out of a client's (unencrypted) HTTP cache. I'm not sure how relevant this is to the API context ofstep-cathough—I've never seen an HTTP client library that caches content. But I guess the poi