-
Updated
Mar 23, 2020 - JavaScript
cache-control
Here are 107 public repositories matching this topic...
-
Updated
Aug 28, 2019 - Python
-
Updated
Jan 20, 2020 - C++
-
Updated
May 6, 2020 - JavaScript
-
Updated
Jan 7, 2020 - PHP
-
Updated
Jan 16, 2018 - PHP
-
Updated
Sep 22, 2017 - PHP
-
Updated
Apr 13, 2019 - Java
-
Updated
Apr 5, 2020 - Ruby
-
Updated
Apr 23, 2020 - JavaScript
First of all, great tool! Nice job on this.
In Firefox, the "share | copy" links in the header are being overlaid by the element in the HTML called <div class="resultHeader">. So in Firefox, you can't actually use those links because they're overlaid by the element due to the margin-top: -40px in the CSS.
I'm not entirely sure why the same problem doesn't occur in Chrome, because it also
-
Updated
May 25, 2020 - JavaScript
-
Updated
Jun 24, 2015 - Python
-
Updated
May 10, 2020 - C#
Update the documentation (including godoc) to be more proper and understandable
-
Updated
May 26, 2020 - Scala
-
Updated
May 24, 2016 - JavaScript
-
Updated
Apr 10, 2020 - Ruby
aw / CacheRules
-
Updated
Jul 15, 2018 - Ruby
-
Updated
Jul 24, 2017 - Java
-
Updated
May 17, 2019 - Swift
-
Updated
Feb 22, 2018 - PHP
-
Updated
Oct 23, 2017 - PHP
-
Updated
Apr 13, 2020 - Go
-
Updated
Apr 10, 2019 - JavaScript
-
Updated
Feb 17, 2017 - Java
Improve this page
Add a description, image, and links to the cache-control topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the cache-control topic, visit your repo's landing page and select "manage topics."
Currently 301 redirects are not cached at all unless the website returns a satisfying
cache-controlheader. This is not how browsers work.https://stackoverflow.com/questions/9130422/how-long-do-browsers-cache-http-301s
There should be a setting to cache 301 redirects for an arbitrary default time.