www-infrastructure-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christopher Tubbs (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (INFRA-9148) git clone to non-TLS url fails with some versions of git
Date Tue, 10 Feb 2015 04:58:34 GMT

    [ https://issues.apache.org/jira/browse/INFRA-9148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14313565#comment-14313565

Christopher Tubbs commented on INFRA-9148:

That seems reasonable. However, the git.apache.org mirror only appears to support the git
protocol (port 9418), and not http, and that may be problematic for some users behind corporate
firewalls or on public WiFi access points. The only HTTP option appears to be on the git-wip
servers (which are also, incidentally, listed as alternates on http://git.apache.org).

As I said, I'm sure it's probably not worth fixing, but it does appear that the git-wip servers
serve a purpose more than just committer access... otherwise, why support non-secure HTTP
at all on those servers?

> git clone to non-TLS url fails with some versions of git
> --------------------------------------------------------
>                 Key: INFRA-9148
>                 URL: https://issues.apache.org/jira/browse/INFRA-9148
>             Project: Infrastructure
>          Issue Type: Bug
>          Components: Git
>            Reporter: Christopher Tubbs
>            Assignee: Jake Farrell
>            Priority: Trivial
> It was pointed out to me today that cloning fails with some URLs, such as:
> http://git-wip-us.apache.org/repos/asf/hadoop.git
> due to some versions of git (in particular, version 1.7.1 in RHEL 6 and CentOS 6) not
complying with http://tools.ietf.org/html/rfc2616#section-10.3.2
> In particular, git relies on the default libcurl behavior which converts the POST request
to a GET request when following the 301 redirect that the above URL does, which results in
"error: RPC failed; result=22, HTTP code = 405". I can't find any configuration option which
instructs git/libcurl to use an alternate behavior (such as curl's --post301 option).
> One work-around is to use https instead of http. Another is to use a different version
of git (not always possible).
> INFRA could handle this situation for users by issuing a 307 redirect instead of a 301
redirect. It might even be able to check the user-agent string to only do this for older versions
of git. (git 1.8.3 and newer work fine).
> I set this initially at "Trivial" priority, because I don't know if this is worth the
effort. Many users will probably easier to use the https url to clone from, or aren't affected,
because they have a newer version of git.

This message was sent by Atlassian JIRA

View raw message