threads / discuss / 30800

git clone over HTTP returns 500 on invalid host name

Subject: git clone over HTTP returns 500 on invalid host name

## tl;dr

3 messages between Jun 13, 2012 and Jun 13, 2012.

replies: 2people: 2as markdown or json

Shawn Pearce· Jun 13, 2012, 23:36 UTC · lore

$ git clone https://this.host.does.not.exist/foo Cloning into 'foo'... error: The requested URL returned error: 500 while accessing http://this.host.does.not.exist/foo/info/refs fatal: HTTP request failed

Hmm. Telling me the host doesn't exist is more useful than 500:

$ git clone git://this.host.does.not.exist/foo Cloning into 'foo'... fatal: Unable to look up this.host.does.not.exist (port 9418) (Name or service not known)

Does anyone care about this other than me?  :-)

Junio C Hamano· Jun 13, 2012, 23:40 UTC · re: Shawn Pearce · lore

Re: git clone over HTTP returns 500 on invalid host name

Shawn Pearce <spearce@spearce.org> writes:

Show 16 quoted lines

> $ git clone https://this.host.does.not.exist/foo
> Cloning into 'foo'...
> error: The requested URL returned error: 500 while accessing
> http://this.host.does.not.exist/foo/info/refs
> fatal: HTTP request failed
>
>
> Hmm. Telling me the host doesn't exist is more useful than 500:
>
> $ git clone git://this.host.does.not.exist/foo
> Cloning into 'foo'...
> fatal: Unable to look up this.host.does.not.exist (port 9418) (Name or
> service not known)
>
>
> Does anyone care about this other than me?  :-)

$ git clone https://this.host.does.not.exist/foo Cloning into 'foo'... error: Couldn't resolve host 'this.host.does.not.exist' while accessing https://this.host.does.not.exist/foo/info/refs fatal: HTTP request failed

What are we doing differently? Perhaps you have a custom proxy that throws 500 back at you or something?

Shawn Pearce· Jun 13, 2012, 23:43 UTC · re: Junio C Hamano · lore

Re: git clone over HTTP returns 500 on invalid host name

On Wed, Jun 13, 2012 at 4:40 PM, Junio C Hamano <gitster@pobox.com> wrote:

Show 27 quoted lines

> Shawn Pearce <spearce@spearce.org> writes:
>
>> $ git clone https://this.host.does.not.exist/foo
>> Cloning into 'foo'...
>> error: The requested URL returned error: 500 while accessing
>> http://this.host.does.not.exist/foo/info/refs
>> fatal: HTTP request failed
>>
>>
>> Hmm. Telling me the host doesn't exist is more useful than 500:
>>
>> $ git clone git://this.host.does.not.exist/foo
>> Cloning into 'foo'...
>> fatal: Unable to look up this.host.does.not.exist (port 9418) (Name or
>> service not known)
>>
>>
>> Does anyone care about this other than me?  :-)
>
>
> $ git clone https://this.host.does.not.exist/foo
> Cloning into 'foo'...
> error: Couldn't resolve host 'this.host.does.not.exist' while accessing https://this.host.does.not.exist/foo/info/refs
> fatal: HTTP request failed
>
> What are we doing differently?  Perhaps you have a custom proxy that
> throws 500 back at you or something?

Grrr. Yes. Its the contrib/persistent-https proxy that is causing this, and a url.insteadof in ~/.gitconfig that always uses it for https:

  [url "persistent-https://"]
    insteadof = https://