Every repository with this icon (
Every repository with this icon (
| Fork of chneukirchen/rack | |
| Description: | a modular Ruby webserver interface edit |
-
The first ip is the client ip. Why is the last ip returned by request.ip?
Comments
-
Invalid byte sequence in US-ASCII with file upload
1 comment Created 4 months ago by thillersonWhen uploading a file I get this error:
/!\ FAILSAFE /!\ 2009-07-03 09:31:48 -0600 Status: 500 Internal Server Error invalid byte sequence in US-ASCII /Users/tonyh/work/captioncontest/vendor/gems/rack-1.0.0/lib/rack/utils.rb:324:in `=~' /Users/tonyh/work/captioncontest/vendor/gems/rack-1.0.0/lib/rack/utils.rb:324:in `block in parse_multipart' /Users/tonyh/work/captioncontest/vendor/gems/rack-1.0.0/lib/rack/utils.rb:319:in `loop' /Users/tonyh/work/captioncontest/vendor/gems/rack-1.0.0/lib/rack/utils.rb:319:in `parse_multipart' /Users/tonyh/work/captioncontest/vendor/gems/rack-1.0.0/lib/rack/request.rb:141:in `POST' /Users/tonyh/work/captioncontest/vendor/gems/rack-1.0.0/lib/rack/methodoverride.rb:15:in `call' /Users/tonyh/work/captioncontest/vendor/rails/actionpack/lib/action_controller/params_parser.rb:15:in `call'I'm using:
Ruby 1.9.1p129 (2009-05-12 revision 23412) [i386-darwin9] RubyGems version 1.3.1 Rack version 1.0 Rails version 2.3.2 Active Record version 2.3.2 Action Pack version 2.3.2 Active Resource version 2.3.2 Action Mailer version 2.3.2 Active Support version 2.3.2I get this error when testing with cucumber/webrat and also through Webrick (since I haven't gotten Mongrel working)
Comments
-
I kept getting this error in my fastcgi.crash.log
This error occurs in lib/rack/handler/fastcgi.rb at line 7
Looks like it's trying to alias a method before the method is created.
I believe line 7 needs moved to below the 'read' method definition.
This error occurred on a Bluehost server with the rack-1.0.0 gem.
Comments
-
Offer :encode => false option to bypass cookie value escaping
0 comments Created about 1 month ago by cgriegoRack encodes all cookie values using URI escaping but this is not a requirement of the cookie spec and thus should be exposed as an option that can be overridden. This is especially true when sharing cookies with other environments such as legacy applications or JavaScript that do not make the same assumptions about the encoding of a cookie. One example is YUI's Cookie utility and its subcookie functionality which uses cookies in a format of "cookiename=subcookie1=foo&sub2=bar" which cannot be achieved with the current Rack::Response#set_cookie method.
Some discussion about cookie encoding: http://www.nczonline.net/blog/2009/05/05/http-cookies-explained/
Comments
-
Hi!
Please have a look at this line:
http://github.com/rack/rack/blob/663abfce9b71ab273c8adc0e76c233671bc43e1d/lib/rack/response.rb#L64
value[:expires].clone.gmtime.strftime("%a, %d-%b-%Y %H:%M:%S GMT")
My default system locale is ru_RU.UTF8, therefore this line produces
string with Russian letters. Browsers cant set expiration date in
Russian. FF sets session cookies, Safari doesnt set cookies at all.
Suppose this is a bug. Instead of strftime, rfc2822 should be used.Thanks.
Comments
-
multipart parser bug (with test to reproduce and fix)
0 comments Created 22 days ago by bloomHi there,
Found a non-obvious bug in rack's multipart parser.
Have a look at:
http://github.com/bloom/rack/commit/8f4bfced74e7a07d0f0f47705b763c7efc2f2aa7
Please let me know how you feel about this, and feel free to cherry pick it if it's interesting. FWIW, I kept running into the oddest problem with a Rails app that happened to be using a multipart form to submit a fairly large form. It so happened that for a given multipart payload size, I would reliably fall onto a chunking/splitting in rack's multipart parser which, given the 16384 bufsize being used by default, just so happened to expose a bug in the parser. Non-obvious because it took a while to isolate and peg down.
Best,
BoskoComments
-
{ :foo => [1,2] }should produce
foo[]=1&foo[]=2not
foo=1&foo=2Comments
visionmedia
Tue Nov 10 08:19:23 -0800 2009
| link
Nevermind, my installed version does not have build_nested_query for some reason












Can anyone comment on this issue? Or is this the wrong place to post issues/bugs for rack?