You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@infra.apache.org by "#asfinfra IRC Bot (JIRA)" <ji...@apache.org> on 2013/05/21 03:06:13 UTC
[jira] [Commented] (INFRA-6244) 404 when following link from
mail-search to archived message
[ https://issues.apache.org/jira/browse/INFRA-6244?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13662541#comment-13662541 ]
#asfinfra IRC Bot commented on INFRA-6244:
------------------------------------------
<danielsh> Also happens in public archives: http://mail-archives.apache.org/mod_mbox/oodt-dev/201304.mbox/%3CCD80E8CA.CEA8%25Daniel.J.Crichton@jpl.nasa.gov%3E
> 404 when following link from mail-search to archived message
> ------------------------------------------------------------
>
> Key: INFRA-6244
> URL: https://issues.apache.org/jira/browse/INFRA-6244
> Project: Infrastructure
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: Mail Archives
> Environment: https://mail-search.apache.org/pmc/private-arch/oodt-private/
> Reporter: Sean Kelly
>
> I'm trying to view an archived message in the oodt-private list archive. The message was posted by "Crichton, Daniel J (4231)" on Tue, 30 Apr, 22:51, with the subject "Re: [VOTE] Arni Sumarlidason as Apache OODT committer and PMC member" and message ID <CD...@jpl.nasa.gov>.
> However, when clicking the subject to go to the message, mail-search.apache.org returns HTTP 404 Not Found.
> This occurs at the following locations:
> * The date view at https://mail-search.apache.org/pmc/private-arch/oodt-private/201304.mbox/date
> * The author view at https://mail-search.apache.org/pmc/private-arch/oodt-private/201304.mbox/author
> * The threaded view at https://mail-search.apache.org/pmc/private-arch/oodt-private/201304.mbox/thread
> This occurs with the following browsers:
> * Safari 6.0.4 (8536.29.13)
> * Firefox 20.0
> * Chrome 26.0.1410.65
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira