You are viewing a plain text version of this content. The canonical link for it is here.
Posted to infrastructure-issues@apache.org by "Sebb (JIRA)" <ji...@apache.org> on 2011/06/20 19:02:48 UTC

[jira] [Created] (INFRA-3719) Mirrors that don't serve headers and footers properly

Mirrors that don't serve headers and footers properly
-----------------------------------------------------

                 Key: INFRA-3719
                 URL: https://issues.apache.org/jira/browse/INFRA-3719
             Project: Infrastructure
          Issue Type: Bug
      Security Level: public (Regular issues)
          Components: Mirrors
            Reporter: Sebb


The following mirrors are not serving headers and footers properly:

http://mirror.pop-sc.rnp.br/apache/commons - No header & no footer - Cherokee
http://apache.mirrors.evolva.ro/commons - No header & no footer - unknown
http://mirror.nus.edu.sg/apache/commons - No header & no footer - nginx/0.7.65
http://apache.ntu.edu.tw/commons - No header & no footer - Apache
http://mirror-fpt-telecom.fpt.net/apache/commons - No header & no footer - nginx

In the case of the ftp.net, it looks as though the server has been configured to serve HEADER.html from the top-level directory, rather than from the current directory.
It is also completely broken HTML as the HEADER.html is included in the page *before* <!DOCTYPE and <html> !!

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Commented] (INFRA-3719) Mirrors that don't serve headers and footers properly

Posted by "Henk Penning (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/INFRA-3719?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13053544#comment-13053544 ] 

Henk Penning commented on INFRA-3719:
-------------------------------------

did send mail to the first four (cc apmirror, ignore) ;
please ignore http://mirror-fpt-telecom.fpt.net :
this is in Vietnam ; they are struggling.

HPP

> Mirrors that don't serve headers and footers properly
> -----------------------------------------------------
>
>                 Key: INFRA-3719
>                 URL: https://issues.apache.org/jira/browse/INFRA-3719
>             Project: Infrastructure
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: Mirrors
>            Reporter: Sebb
>
> The following mirrors are not serving headers and footers properly:
> http://mirror.pop-sc.rnp.br/apache/commons - No header & no footer - Cherokee
> http://apache.mirrors.evolva.ro/commons - No header & no footer - unknown
> http://mirror.nus.edu.sg/apache/commons - No header & no footer - nginx/0.7.65
> http://apache.ntu.edu.tw/commons - No header & no footer - Apache
> http://mirror-fpt-telecom.fpt.net/apache/commons - No header & no footer - nginx
> In the case of the ftp.net, it looks as though the server has been configured to serve HEADER.html from the top-level directory, rather than from the current directory.
> It is also completely broken HTML as the HEADER.html is included in the page *before* <!DOCTYPE and <html> !!

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Commented] (INFRA-3719) Mirrors that don't serve headers and footers properly

Posted by "Gavin (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/INFRA-3719?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13058227#comment-13058227 ] 

Gavin commented on INFRA-3719:
------------------------------

pop-ms still not compliant
evolva.ro still not compliant
nus.edu.sg are showing header/footer now but still nginx
ntu.edu still not compliant
(ignoring vietnam)

Henk, they have had 8 days, unless objections I'll remove the first 4 mirrors mentioned later today.

> Mirrors that don't serve headers and footers properly
> -----------------------------------------------------
>
>                 Key: INFRA-3719
>                 URL: https://issues.apache.org/jira/browse/INFRA-3719
>             Project: Infrastructure
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: Mirrors
>            Reporter: Sebb
>
> The following mirrors are not serving headers and footers properly:
> http://mirror.pop-sc.rnp.br/apache/commons - No header & no footer - Cherokee
> http://apache.mirrors.evolva.ro/commons - No header & no footer - unknown
> http://mirror.nus.edu.sg/apache/commons - No header & no footer - nginx/0.7.65
> http://apache.ntu.edu.tw/commons - No header & no footer - Apache
> http://mirror-fpt-telecom.fpt.net/apache/commons - No header & no footer - nginx
> In the case of the ftp.net, it looks as though the server has been configured to serve HEADER.html from the top-level directory, rather than from the current directory.
> It is also completely broken HTML as the HEADER.html is included in the page *before* <!DOCTYPE and <html> !!

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Closed] (INFRA-3719) Mirrors that don't serve headers and footers properly

Posted by "Gavin (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/INFRA-3719?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gavin closed INFRA-3719.
------------------------

    Resolution: Fixed
      Assignee:     (was: Gavin)

removed pop-sc, evolva, ntu.edu.tw - others have headers/footers back.

> Mirrors that don't serve headers and footers properly
> -----------------------------------------------------
>
>                 Key: INFRA-3719
>                 URL: https://issues.apache.org/jira/browse/INFRA-3719
>             Project: Infrastructure
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: Mirrors
>            Reporter: Sebb
>
> The following mirrors are not serving headers and footers properly:
> http://mirror.pop-sc.rnp.br/apache/commons - No header & no footer - Cherokee
> http://apache.mirrors.evolva.ro/commons - No header & no footer - unknown
> http://mirror.nus.edu.sg/apache/commons - No header & no footer - nginx/0.7.65
> http://apache.ntu.edu.tw/commons - No header & no footer - Apache
> http://mirror-fpt-telecom.fpt.net/apache/commons - No header & no footer - nginx
> In the case of the ftp.net, it looks as though the server has been configured to serve HEADER.html from the top-level directory, rather than from the current directory.
> It is also completely broken HTML as the HEADER.html is included in the page *before* <!DOCTYPE and <html> !!

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Assigned] (INFRA-3719) Mirrors that don't serve headers and footers properly

Posted by "Gavin (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/INFRA-3719?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gavin reassigned INFRA-3719:
----------------------------

    Assignee: Gavin

> Mirrors that don't serve headers and footers properly
> -----------------------------------------------------
>
>                 Key: INFRA-3719
>                 URL: https://issues.apache.org/jira/browse/INFRA-3719
>             Project: Infrastructure
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: Mirrors
>            Reporter: Sebb
>            Assignee: Gavin
>
> The following mirrors are not serving headers and footers properly:
> http://mirror.pop-sc.rnp.br/apache/commons - No header & no footer - Cherokee
> http://apache.mirrors.evolva.ro/commons - No header & no footer - unknown
> http://mirror.nus.edu.sg/apache/commons - No header & no footer - nginx/0.7.65
> http://apache.ntu.edu.tw/commons - No header & no footer - Apache
> http://mirror-fpt-telecom.fpt.net/apache/commons - No header & no footer - nginx
> In the case of the ftp.net, it looks as though the server has been configured to serve HEADER.html from the top-level directory, rather than from the current directory.
> It is also completely broken HTML as the HEADER.html is included in the page *before* <!DOCTYPE and <html> !!

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira