GitHub user sebbASF opened an issue:
Bug: unhelpful error reporting for invalid Permalinks/Source links
An invalid Permalink, for example:
results in a blank screen. It's not obvious whether the request is still
being processed. The code should display a suitable error message.
The corresponding invalid Source URL:
results in the message:
/var/www/ponymail_asf/site/api/lib/elastic.lua:31: Backend Database
returned code 404!"
Although it is clear that something has gone wrong, it's not obvious what
the problem is.
The code should report "Message not found" or something similar.
Note that if a Source URL refers to a private message, then the response is
"You must be logged in to view this email"
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket