search for: httpparsererror

...e sandbox due to security. I''m using as3httpclientlib as HTTPService doesn''t do the job. Flash sends a request <policy-file-request/> over the socket and expects the policy file back. This is not HTTP so I get: HTTP parse error, malformed request (127.0.0.1): #<Mongrel::HttpParserError: Invalid HTTP format, parsing fails.> REQUEST DATA: "<policy-file-request/>\000" This post seems to be the way but I have no idea where to put the code. http://clockingit.wordpress.com/2007/01/25/juggernaut-comet-fixes/#comment-1515 . Question: Using how/where do I intercept th...

...UP => reload (without restart). It might not work well. But that message only occurs during mongrel startup. When I attempt to access my website via www.xyz.com or xyz.com I get a ton of mongrel errors complaining that HTTP parse error, malformed request (127.0.0.1): #<Mongrel::HttpParserError: Invalid HTTP format, parsing fails.> REQUEST DATA: "GET /images/Logo 010 - 200x48 - no background.png?1289857922 HTTP/1.1\r\nHost: 127.0.0.1:12001\r\nUser-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.2.12) Gecko/20101026 Firefox/3.6.12 ( .NET CLR 3.5.30729; .NET4.0E)\r\...

...e just migrated my system over to a new macbook. I''ve been having a nightmare today trying to get the site I''m working on to work... All gems are in place, MySQL etc. However - I am stuck on this error form Mongrel: HTTP parse error, malformed request (127.0.0.1): #<Mongrel::HttpParserError: Invalid HTTP format, parsing fails.> The only thing it could be, I think, is we are using the SSL_Requirement plugin. That is redirecting to an https page and thats the last thing that happens before mongrel shows this error. I have never seen this before, and google searches are not showing...

...a URL that gets passed to mongrel, it will return a Bad Request error. Kind of odd that "http://localhost/%" causes a "Bad Request" instead of a "Not Found" error. Here is the error from the mongrel log: HTTP parse error, malformed request (127.0.0.1): #<Mongrel::HttpParserError: Invalid HTTP format, parsing fails.> I''m using Nginx in front of mongrel. I understand this is a bad URL, but is there anyway to have mongrel ignore lone percent signs? Or perhaps a Nginx rewrite rule that will encode extraneous percent signs? -- Posted via http://www.ruby-forum.co...

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 CST 2006: BAD CLIENT (192.168.1.2): Invalid HTTP format, parsing fails. 0.3.13.5

...client, e) code = case e - when EOFError,Errno::ECONNRESET,Errno::EPIPE,Errno::ENOTCONN - # client disconnected on us and there''s nothing we can do when Unicorn::RequestURITooLongError 414 when Unicorn::RequestEntityTooLargeError @@ -556,8 +554,12 @@ class Unicorn::HttpServer when Unicorn::HttpParserError # try to tell the client they''re bad 400 else - Unicorn.log_error(@logger, "app error", e) - 500 + if client.closed? + # client disconnected on us and there''s nothing we can do + else + Unicorn.log_error(@logger, "app error", e) + 500 + end end if code client.k...

...e. What I''m having trouble with is the Apache/SSL/mod_proxy/mongrel/ Rails stack. If I try to reach the site with https://new.identry.com, I get the following error in the mongrel.log: Thu Jan 17 09:10:57 -0500 2008: HTTP parse error, malformed request (75.127.142.66): #<Mongrel::HttpParserError: Invalid HTTP format, parsing fails.> Thu Jan 17 09:10:57 -0500 2008: REQUEST DATA: "\200=\001\003\000\000$ \000\000\000\020\000\0009\000\0008\000\0005\000\0003\000\0002\000\000 \004\000\000\005\000\000/\000\000\026\000\000\023\000\376\377\000\000 \n\243?S\376?????|\255??y" --- PA...

This is important so please read this message very carefully. There is a DoS for Ruby''s cgi.rb that is easily exploitable. The attack involves sending a malformed multipart MIME body in an HTTP request. The full explanation of the attack as well as how to fix it RIGHT NOW is given below. Most of the work was done by Jeremy Kemper and Jamis Buck. They did all the work of building the