From: Alan Sargent <alsarg72@gmail.com>
To: Ilari Liusvaara <ilari.liusvaara@elisanet.fi>
Cc: git@vger.kernel.org
Subject: Re: fatal: protocol error: bad line length character: GET <<<<<
Date: Wed, 26 Jan 2011 14:40:27 +0800 [thread overview]
Message-ID: <AANLkTin2Fn4mbrrDF4ceEYQZoyGRNymsk0aouBaUp94-@mail.gmail.com> (raw)
In-Reply-To: <20110126055955.GA13304@LK-Perkele-VI.localdomain>
Ah! Thank you very much.
:)
On Wed, Jan 26, 2011 at 1:59 PM, Ilari Liusvaara
<ilari.liusvaara@elisanet.fi> wrote:
> On Wed, Jan 26, 2011 at 12:53:11PM +0800, Alan Sargent wrote:
>> Hello,
>>
>> The "fatal: protocol error: bad line length character" seems fairly
>> common, but in the archive and the faq there isn't reference to this
>> particular instances - GET.
>>
>> alan@toaster:~$ git init myrepo
>> Initialized empty Git repository in /home/nev/myrepo/.git/
>> alan@toaster:~$ cd myrepo
>> alan@toaster:~/myrepo$ git daemon
>> fatal: protocol error: bad line length character: GET << just hitting
>> F5 in the browser
>> fatal: protocol error: bad line length character: GET
> [...]
>
> Git daemon serves git:// protocol, not HTTP, you can't access it from
> web browser.
>
> If you are looking for Git repository web interface, look at gitweb
> or cgit.
>
> The error is because HTTP begins the request with "GET " and git
> daemon is trying to interpret that as length of packet, failing
> and spitting out a fatal error.
>
> -Ilari
>
prev parent reply other threads:[~2011-01-26 6:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-26 4:53 fatal: protocol error: bad line length character: GET <<<<< Alan Sargent
2011-01-26 5:59 ` Ilari Liusvaara
2011-01-26 6:40 ` Alan Sargent [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=AANLkTin2Fn4mbrrDF4ceEYQZoyGRNymsk0aouBaUp94-@mail.gmail.com \
--to=alsarg72@gmail.com \
--cc=git@vger.kernel.org \
--cc=ilari.liusvaara@elisanet.fi \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).