[9.x] Add 402 exception view#45682
Merged
Merged
Conversation
This was referenced May 29, 2023
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Currently no error page exists for exceptions with an HTTP status code of 402 Payment Required.
Even though it's a nonstandard response status code, it's used by multiple large companies to indicate functionality limited due to a payment being required.
Personally, I'm using it in a SaaS project where certain features are only available on a paid plan. If the locked functionality involves entire (public-facing) pages/routes, it makes sense to show a default error view. For example: when users who are not entitled to use the paid feature of embedding a scheduling page on their own site still try to embed the page, they should be greeted with the new 402 exception view.