Move from 301 to 302 redirects (less caching issues) #32
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
OctoDNS Plan for
|
||||||||||||||||||||||||
| Operation | Name | Type | TTL | Value | Source |
|---|---|---|---|---|---|
| Update | TXT | 120 | 301 https://g0v.tw/intl/en/ admin=patcon |
||
| 120 | 302 https://g0v.tw/intl/en/ admin=patcon |
config-files | |||
| Summary: Creates=0, Updates=1, Deletes=0, Existing Records=5 | |||||
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
(Started this without realizing 302 redirects weren't possible)
Browsers cache 301 redirects in a way that's hard to clear, since we're never actually on the subdomain long enough to refresh or use chrome devtools.
Blocked by ronnywang/301-service#1
Before merging, should change all the other 301 redirects in this repo to 302s as well.