You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ponymail.apache.org by sebbASF <gi...@git.apache.org> on 2016/09/15 09:29:08 UTC

[GitHub] incubator-ponymail issue #123: Bug: unhelpful error reporting for invalid Pe...

GitHub user sebbASF opened an issue:

    https://github.com/apache/incubator-ponymail/issues/123

    Bug: unhelpful error reporting for invalid Permalinks/Source links

    An invalid Permalink, for example:
    
    https://lists.apache.org/thread.html/wxyz@%3Cdev.ponymail.apache.org%3E
    
    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:
    
    https://lists.apache.org/api/source.lua/wxyz@%3Cdev.ponymail.apache.org%3E
    
    results in the message:
    
    "Error!
    
    /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 the helpful:
    "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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] incubator-ponymail issue #123: Bug: unhelpful error reporting for invalid Pe...

Posted by asfgit <gi...@git.apache.org>.
Github user asfgit closed the issue at:

    https://github.com/apache/incubator-ponymail/issues/123


---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---