Change path matching in Caddyfile: #2604
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.
Path matching in the Caddyfile has been broken for a long time, we just never noticed because we were serving out the same content over every route and akamai was covering over the difference with rewrites. Now that akamai is fixed and our standard caddy config has changed the problem in chrome is biting us. I tested this locally by downloading the latest chrome image, running it locally docker, confirming I couldn't get anything over beta routes, making the change, and confirming it works.