[jira] [Closed] (INFRA-7281) Index pages in repository.a.o/content/ use HTTP links (Those should be HTTPS ones)

["Brian Fox (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/INFRA-7281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Fox closed INFRA-7281.
----------------------------

    Resolution: Won't Fix

Only authenticated actions are required over https, everything else is also allowed via http. Just adjust your initial url to be http and you won't see the redirects.



> Index pages in repository.a.o/content/ use HTTP links (Those should be HTTPS ones)
> ----------------------------------------------------------------------------------
>
>                 Key: INFRA-7281
>                 URL: https://issues.apache.org/jira/browse/INFRA-7281
>             Project: Infrastructure
>          Issue Type: Bug
>          Components: Nexus
>            Reporter: Konstantin Kolinko
>
> I am using wget to download snapshot repository for an upcoming Tomcat release.  For reference, my command looks like the following:
> wget -r --no-parent -e robots=off --level inf https://repository.apache.org/content/repositories/orgapachetomcat-1005/
> The issue is that the index pages list their contents with http links. 
> E.g. the above mentioned "orgapachetomcat-1005" page contains the following link:
> <a href="http://repository.apache.org/content/repositories/orgapachetomcat-1005/org/">org/</a>
> This results in the following behaviour:
> 1. wget downloads the index page using HTTPS on port 443
> 2. wget follows the link and re-connects to port 80
> 3. server replies with "302 Found" with redirect to HTTPS
> 4. wget re-connects to port 443.
> The bad consequences are:
> 1) This is slow. Instead of several minutes such download takes more than an hour.  Wget is unable to reuse existing connection, and there is some timeout with HTTP responses.
> 2) There is HTTP traffic, when the server is supposed to be accessed securely via HTTPS.
> I suspect that the server that is running Nexus does not know that it being accessed via HTTPS. This should be possible to solve via server configuration.
> Alternatively, the index pages could return relative links, e.g.
> <a href="org/">org/</a>



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)