* Add Rack::Auth.add_scheme to enable folks to fix anything that breaks * Add common auth schemes, MS ones, AWS ones, etc are missing, as unlikely * Checked Rails - they don't use our authorization code * Checked Warden - uses rails * Checked Omniauth - uses rails * Checked doorkeeper - users rails * Checked rack-authentication - does it's own thing * Checked warden-oauth - doesn't do headers * Checked devise - uses rails * Checked oauth2-rack - header creation only * Checked rack-oauth2-server - does it's own thing * Probably missed a bunch, but that'll have to do
Fix parsing miltiple ranges in HTTP_RANGE header according to w3 rfc2616 (according to last example in sec14.35.1 http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.35.1 ) (according to BNF rules in http://www.w3.org/Protocols/rfc2616/rfc2616-sec2.html#sec2.1 )
Date: Mon, 22 Oct 2012 10:29:22 -0400 Message-ID: <CAH6G9XNkVkUWh9JPT9HuHzJ4KmRNoPSr8ov3q0rgzH3b=u3cGw@mail.gmail.com> On Mon, Oct 22, 2012 at 10:17 AM, Christian Neukirchen <firstname.lastname@example.org> wrote: > Is it ok to put the other files as MIT license into contrib/? > (Perhaps add a copyright message to the .svg) Whatever you want, they're all yours. Thanks!
`rackup -h` says '-I' can be used more than once. However, instead of adding each value to $LOAD_PATH, rackup would discard the value of all but the last '-I' option. Signed-off-by: Anurag Priyam <email@example.com>
Example of these cookies would be: "foo=bar,;bar=foo" or ",foo=bar;," Conflicts: test/spec_utils.rb