similar to: BAD CLIENT error with mobile phone access

Hi I was interested to see how Mongrel uses Lex/Yacc to parse the HTTP requests using a Regal generated parser. I downloaded the source but do not see the lex and yacc files...

Hey Zed, any chance you mind sharing the grammar file you use with lemon to create the parser? I''ve been meaning to sit down and learn how to use one of those things. If not, any suggestions on a good resource for learning how to use a LALR parser?

Hi, I''m looking for suggestions on the simplest way to implement an HTTP proxy under Rails/Mongrel. It should preserve ALL of the proxied HTTP response - including all header content such keepalives, etc. Yes, I know I can do this with Apache''s proxy module, and we already do that for the non-development/test environments. This is just for the development/test environment

Before anything else, let me state this: Of course it''s going to be PAINFULLY slow on MRI. That''s not the point :) I thought I''d try out writing out a Ruby version of the parser for the purposes of Rubinius. For those of you who aren''t aware, Ragel supports a goto-driven FSM on Rubinius by injecting assembly directly, and Rubinus head honcho guy Evan Phoenix

Hey so, People are asking about Mongrel Ruby 1.9 compatibility. Isn''t the point of 1.9 for library developers to have time to get ready for 2.0? It''s not like 1.9 is a production release. Evan -- Evan Weaver Cloudburst, LLC

This is off-topic. I''m hoping someone on this list can point me towards more general information on finite state machines, their definition, how to build them, determining when to apply them, etc. I read Zed''s blog entry from way back when covering Ragel [1] but he hasn''t followed it up and there aren''t many pointers to external information.

Hi folks, I have a problem with a storage web service our group wrote using Mongrel::HttpHandler We have a consistent problem when using http PUT to this service when the data is larger than about 4 GB. The web service actually retrieves and processes the data, but the clients hang - the TCP connection is still in the ESTABLISHED state on the client side, but the TCP session no longer exists on

I''m taking a stab at creating a parser to parse the server response using the mongrel parser as a base. Never having used a parser like Ragel before in my life, I''d like some input on the following for parsing an http server response. This is part of my modified version of http11_parser.rl. In particular what would be better than using ''any'' to match the

hi, I rewrote escape, unescape, and query_parse in a C extension. http://s3.amazonaws.com/four.livejournal/20070922/http_helpers.tar.bz2 Here are some sample benchmarks (the benchmark script is included in the package) user system total real escape: Single long Mongrel: 1.680000 0.020000 1.700000 ( 1.837793) HttpHlp: 0.030000 0.010000 0.040000 ( 0.036590)

Hi Zed, I checked in a pure-Ruby URI classifier to Mongrel trunk. Ola''s Java port of the TST had some bug, and I don''t think it''s necessary in the first place. The Ruby classifier is around 25 lines instead of the 400-odd lines for the C extension and the 200-odd for the Java extension. It uses a Regexp which is perhaps shady: @matcher = Regexp.new(routes.map do

I''ve gone through the mailing list archives and looked through all the docs I could find but I still can''t figure out exactly what''s going on with my Mongrel that it gives the following error: [Timestamp]: BAD CLIENT (127.0.0.1): Invalid HTTP format, parsing fails I''m running Cygwin 1.5.20-1, Ruby 1.8.4, and WinXP. I''d appreciate any help on getting

Hi Jason ! Hmmm, this is good and bad news: Good: ruby hooks means I could use a single pass to parse textile customizations in zena instead of running two parsers: nice. Bad: I have just switched to ragel for QueryBuilder to parse pseudo sql and I fear your shortcomings (if that''s an english phrase). Could you describe more precisely what you are missing with ragel ? I''m

Hello. Some time ago I committed a Rubinius assembly-based HTTP parser generated from Ragel to the Rubinius git repository. Yesterday I made a Mongrel gem which installs and works on Rubinius. This basically involved commenting out anything to do with fastthread or the http11 C extension. If there''s interest in releasing a Rubinius-targeted gem, I can make changes to the Rakefile to

Hello, is anyone on the list using a normal cell/mobile phone which is able to act as a SIP client over WLAN? Or has anyone heard of a SIP client for cell/mobile phones running windows mobile 6.x? The phone should use SIP, when the asterisk server is reachable and should automatically switch to a German telco if it is not reachable. Thanks for any hints, Stefan --

Hi, Is there any future possibility that Asterisk will be compatible with connection to 3G video mobile phone such as Nokia 7600, Nokia 6630 and many ohters in Japan, Europe and HongKong? If this become possible, H.323 video clients and 3G mobile phone will be able to share video conversation, which will be huge in those countries. In Japan, more than 3 million 3G video mobile phones are

Hello Mongrel Users, I''m writing a web server called Ebb. It''s written in C, makes use of the Mongrel HTTP parser, and uses libev its event loop. The goal is to be small, fast, and language independent server that can host web frameworks. I have written a small Ruby binding which provides a Rack handler - this will allow Ebb to host Rails, Merb, and other Ruby frameworks. In the

Not strictly asterisk related, however... Here's an odd one for you.. I got a Nokia E90 and setup it's SIP client which runs via Wi-Fi (anyone know if I can make it work via GPRS/3G?) Anyway, in a fit of idleness, I thought I'd see what codecs it supports, as I couldn't find it in the manual... And it supports: ilbc g729 ulaw/alaw No GSM! How odd is that, given

I''m running jruby trunk which has integrated rubygems 1.0.0 and when I try and install mongrel with gem it blows up when the fastthread dependency tries to do a native compilation. I couldn''t find a copy of the gemspec in the svn checkout but looking at the one installed when gem installing mongrel didn''t show any platform differentiation. There is platform

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

Yo Zed, Just curious -- what do you think of the LiteSpeed server? Is it better than Lighty? Does it (gasp!) also serve Rails apps like Mongrel? I think I read that LiteSpeed doesn''t have proxying support. Thanks, Joe __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com