Feature Request P2
Status Update
No update yet.
Comments
jo...@google.com
[Deleted User] <[Deleted User]>
Hello,
Thank you for reaching out to us!
This issue seems to be outside of the scope of Issue Tracker. This Issue Tracker is a forum for end users to report bugs and request features on Google Cloud products. Please go through
I recommend you to
For now, I'm going to close this thread which will no longer be monitored. In case you want to report a new issue, please do not hesitate to create a new Issue Tracker describing your issue.
Thank you!
rb...@google.com
I have forwarded this request to the engineering team. We will update this issue with any progress updates and a resolution.
Description
----------
I refer to the GAE/J documentation
Configuration | Deployment Descriptor | Error Handlers as can be found at
At the bottom of this section there is a note:
"Note: At present, you cannot configure custom error handlers for some error conditions. Specifically, you cannot customize ... or the 500 server error page that appears after an App Engine internal error."
THE REQUEST
-----------
I request that such a configuration be made available for the 500 server error page that appears after a GAE internal error.
REASON WHY I MAKE MY REQUEST
----------------------------
The current presentation of the GAE/J page after this error
"Error: Server Error
The server encountered an error and could not complete your request.
If the problem persists, please report your problem and mention this error message and the query that caused it.
"
appears very unprofessional to visitors to a web site. The presentation of an application-configured web page would result in the same lack of functionality (that is, none) but would enable the development and showing of an application-specific error page which could be:
· professional-looking by maintaining any required page style
· be more informative and helpful to users (who usually cannot be expected to be IT professionals with detailed knowledge of the GAE development and community environment)
· increase customer retention during sporadic or temporary outages.
This page could be enforced to be static and verified to be valid at application upload-time, in order to increase the probability that this page could indeed be shown whilst GAE is having problems.
CONCLUSION
----------
Allowing applications to be configured to present an application-specific error page following such a GAE internal error would improve the user experience - and reduce the exposure of Google to the user for such a problem, too!