Allow Custom Error Pages #1350
Open
Allow Custom Error Pages #1350
Conversation
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
Allow Custom Error Pages as mentioned in [this issue](Azure#733)
|
|
|
@renancnetto Thanks for the proposal. Annotation names look good. |
|
Bump on the progress of this task.... |
|
Another bump, would love to have this! |
|
any update on this? |
|
Another ~half year bump! |
|
Bump ... +1 |
|
@mscatyao , can you review this? |
|
@akshaysngupta @mscatyao We are needing this feature. What can we do to help you speed op the review process? We are waiting for more then two years and other then possitive feedback we do not see any improvements mentioned. Thanks for understanding! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
7 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.
Allow Custom Error Pages as mentioned in this issue
Checklist
Fixes.Description
Added a file proposing allow Custom Error Pages in AGIC in order to resolve the problem highlighted in this issue
Fixes
#733