Backporting the 301 redirect fix to v3 branch #1722
Merged
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.
R: @philipwalton
Fixes #1677
This takes the v4 change from #1678 and backports it to the v3 branch.
After doing some
git
digging, the change that introduced the issue turned out to be https://github.com/GoogleChrome/workbox/pull/828/files#diff-37d7dc9fcc2f99bebe79d4b453e132fe, i.e. it looks inadvertant, so I can't think of a reason why we wouldn't want this code to be in v3.x.