app sends 404 code for /fallback and failing canonical #831
No reviewers
Labels
No labels
area: devops
area: discovery
area: docs
area: livestream
area: proposal
consider soon
dependencies
Epic
good first issue
hacktoberfest
help wanted
icebox
level: 1
level: 2
level: 3
level: 4
needs: exploration
needs: grooming
needs: priority
needs: repro
needs: tech design
on hold
Osprey
priority: blocker
priority: high
priority: low
priority: medium
protocol dependent
resilience
Tom's Wishlist
type: bug
type: discussion
type: error handling
type: improvement
type: new feature
type: refactor
type: task
type: testing
unplanned
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: LBRYCommunity/spee.ch#831
Loading…
Reference in a new issue
No description provided.
Delete branch "fourOhFourCode"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Previously, the 404 page responded with 200 code.
Now it responds with 404 code when specifically the 'fallback' action from the /fallback controller exists.
Previously, an invalid claim such as /abcd/1234 responded with 200 code. Now it responds with a 404 code when canonicalUrl fails.
The home page and other redirects are unaffected.
I added line breaks for you