From: John-Paul Bader <hukl@berlin.ccc.de>
To: unicorn list <mongrel-unicorn@rubyforge.org>
Subject: Re: Usernames in the http_URL
Date: Fri, 18 Dec 2009 10:48:43 +0100 [thread overview]
Message-ID: <1191F787-4539-4877-86A1-C62C8D58DC27@berlin.ccc.de> (raw)
In-Reply-To: <d411cc4a0912171831h8cbeef2wfed676bd11fa2b19@mail.gmail.com>
Hey guys,
I think the <resource_type>://<username>:<password>@<host>/<path> scheme is not "illegal". There are examples of this in the URL RFC, just no explicit HTTP example.
This probably a vague area. Its not in the http rfc and its not explicitly mentioned in the http auth rfc either but in combination with the URL RFC there is at least room for it. I haven't found the paragraph yet which says: no username:password stuff allowed in http urls. But I was just searching through these things … there are good chances I missed it.
http://en.wikipedia.org/wiki/URI_scheme
http://tools.ietf.org/html/rfc2617
http://www.ietf.org/rfc/rfc1738.txt
Anyway, I came across such urls a lot. Often I use them for giving people easy access to an otherwise basic authed resource - in a chat conversation for example. I know apache and nginx support this - IIS does not.
Hrm - tough call ;)
Kind regards, John
_______________________________________________
Unicorn mailing list - mongrel-unicorn@rubyforge.org
http://rubyforge.org/mailman/listinfo/mongrel-unicorn
Do not quote signatures (like this one) or top post when replying
next prev parent reply other threads:[~2009-12-18 9:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-18 0:20 Usernames in the http_URL Scott Chacon
2009-12-18 1:23 ` Eric Wong
2009-12-18 1:32 ` Eric Wong
2009-12-18 2:31 ` Scott Chacon
2009-12-18 9:48 ` John-Paul Bader [this message]
2009-12-19 10:04 ` Eric Wong
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
List information: https://yhbt.net/unicorn/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1191F787-4539-4877-86A1-C62C8D58DC27@berlin.ccc.de \
--to=hukl@berlin.ccc.de \
--cc=mongrel-unicorn@rubyforge.org \
/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.
Code repositories for project(s) associated with this public inbox
https://yhbt.net/unicorn.git/
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).