rack-devel archive mirror (unofficial) https://groups.google.com/group/rack-devel
 help / color / mirror / Atom feed
From: Saito <saitowu@gmail.com>
To: Rack Development <rack-devel@googlegroups.com>
Subject: Rack::Auth can not work with git command?
Date: Wed, 22 Feb 2012 06:08:52 -0800 (PST)	[thread overview]
Message-ID: <f20e9a59-02e3-4966-b35b-baa3cbe2d7bb@vh10g2000pbc.googlegroups.com> (raw)

i have been run a [grack](https://github.com/schacon/grack) server on
my computer.

created and edited a new .netrc file.

`machine localhost login 123 password 456`

then i tested grack by curl:

`curl --netrc --location -v http://localhost/grit.git/HEAD | grep
'ref: refs/heads`

and i can get `auth.username` is `123`

when i do with git command:

`git clone http://localhost/grit.git`

`auth.provided?` is `false`

                 reply	other threads:[~2012-02-22 15:37 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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-list from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://groups.google.com/group/rack-devel

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=f20e9a59-02e3-4966-b35b-baa3cbe2d7bb@vh10g2000pbc.googlegroups.com \
    --to=rack-devel@googlegroups.com \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).