Zed A. Shaw [EMAIL PROTECTED] wrote:
On Mon, 16 Oct 2006 07:48:16 +0800
Eden Li [EMAIL PROTECTED] wrote:
Here's a patch of http_parser.rl against r358 that allows these three
characters and associated unit tests.
Rock on! That's what I'm talking about. I'll apply this soon and
post
Sweet, when can I remove these lines from my nginx.conf ?
--
# nginx does not appear to properly sanitize urls in the form
http://www.redbubble.com/people/photography/art/
/p
# which causes mongrel to slam the door all the way down the cluster,
causing a minor hickup. Both behaviours are
#
On Thu, Mar 27, 2008 at 7:24 PM, Dave Cheney [EMAIL PROTECTED] wrote:
Sweet, when can I remove these lines from my nginx.conf ?
Hold down a bit man, it just got into the code base ;-)
Regards,
--
Luis Lavena
Multimedia systems
-
Human beings, who are almost unique in having the ability to
Starts here:
http://rubyforge.org/pipermail/mongrel-users/2006-August/001162.html
This patch should basically eliminate it, though, I guess :)
Which is awesome.
-Ross.
On 10/16/06, Eden Li [EMAIL PROTECTED] wrote:
Care to point to the thread?
On 10/16/06, Ross Singer [EMAIL PROTECTED] wrote:
IE6 happily sends unsafe* characters unencoded if you've typed them
into the URL bar of your IE6 window. This could happen if you copy
paste a URL from an email or web page.
Mongrel doesn't seem to handle these properly. In 0.3.13.3 it would
print out something like:
Sun Oct 15 23:05:38
On 10/15/06, Eden Li [EMAIL PROTECTED] wrote:
IE6 happily sends unsafe* characters unencoded if you've typed them
into the URL bar of your IE6 window. This could happen if you copy
paste a URL from an email or web page.
Mongrel doesn't seem to handle these properly. In 0.3.13.3 it would
You could probably write a mongrel handler to cuddle with the params.Aren't people likely to blame it on Mongrel, even if it is most unfair ?The usual conclusion is this server can't handle that.
My gut feeling is that a web server should handle gracefully ill-behaved clients or complain
Any examples out there on how I could do this? The docs on rubyforge
are pretty thin in this area. I got as far as authoring a mini
gem_plugin, but:
$ mongrel_rails start -S config/mongrel.conf
** Starting Mongrel listening at 0.0.0.0:3000
** Starting Rails with development environment...
**
Hmm. It looks like a plugin can't handle this. The plugin I tested
never got its process method called.
Tracing through lib/mongrel.rb, the HttpParser#execute method throws
an HttpParserError before it has a chance to pass the request off to
the plugin. Looks like this'll have to be patched in
Here's a patch of http_parser.rl against r358 that allows these three
characters and associated unit tests.
On 10/16/06, Eden Li [EMAIL PROTECTED] wrote:
Hmm. It looks like a plugin can't handle this. The plugin I tested
never got its process method called.
Tracing through lib/mongrel.rb,
This has come up before, btw.
-Ross.
On 10/15/06, Eden Li [EMAIL PROTECTED] wrote:
Hmm. It looks like a plugin can't handle this. The plugin I tested
never got its process method called.
Tracing through lib/mongrel.rb, the HttpParser#execute method throws
an HttpParserError before it has
11 matches
Mail list logo
