Displaying 20 results from an estimated 80000 matches similar to: "Compiling the http 1.1 parser apart issue"
2006 Apr 07
1
HTTP 1.1 parser and non-standard request methods
hi,
i was thinking of creating a WebDAV plugin for mongrel, but ran into an
issue... the http parser hardcodes which request methods it considers
valid, so it blocks non-standard request methods like MKCOL, PROPFIND,
etc. i''m not familiar with the type of grammar being used for the
parser, but is it possible to defer the request method validation to a
later point, possibly inside the
2006 May 27
0
Error in http parser or client?
Hello,
I started a little pet project of making a webdav plugin for mongrel.
First thing I did was get the test suite called litmus from
http://www.webdav.org/neon/litmus/
and run it against a completely dummy handler that doesn''t even try to
handle anything.
Then mongrel said to me:
BAD CLIENT (127.0.0.1): Invalid HTTP format, parsing fails.
REQUEST DATA: DELETE
2008 Apr 24
4
Pure Ruby HTTP parser
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
2006 Sep 25
5
HTTP Parser (Regal)
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...
2006 Apr 04
1
Mongrel Web Server 0.3.12.2 -- Iron Mongrel (Parser Fix)
Hello Everyone,
This is an ultra quick announce for a bug fix release to Mongrel. It
corrects a small change in the HTTP parser that causes an error when people
use multi-part forms in a certain way. The fix is literally 4 characters
changed in the parser specification.
Everyone should update to this release and let me know if their forms act
really weird. I''ve tested various upload
2006 Apr 10
1
Mongrel Web Server 0.3.12.4 -- Relaxed Parser, Date Fix
Hello Everyone,
Just a small announcement for Mongrel 0.3.12.4 which fixes the following
things:
* Corrects the date format returned so that months are three chars only.
* Fixes a problem where DirHandler wasn''t returning Last-Modified and Etag
headers for unknown MIME types.
* Implements a default mime type for anything it doesn''t know about, and
lets you set it via an
2006 Oct 31
5
mongrel parser for server response
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
2009 Sep 15
0
HTTP parser C extension should be Rubinius-compatible
Hi all,
I''ve just pushed out some changes to the C HTTP parser that should make
it compatible with a recent Rubinius[1] using the C API. While I got
the http_parser and http_parser_ng tests to pass with the new changes,
most of the other tests that use pure Ruby actually failed(!).
If anybody wants to pick up where I left off (even if it''s to properly
report bugs to the
2006 Apr 10
0
Mongrel Web Server 0.3.12.4 -- Relaxed Parser, Date Fix
Hello Everyone,
Just a small announcement for Mongrel 0.3.12.4 which fixes the following
things:
* Corrects the date format returned so that months are three chars only.
* Fixes a problem where DirHandler wasn''t returning Last-Modified and Etag
headers for unknown MIME types.
* Implements a default mime type for anything it doesn''t know about, and
lets you set it via an
2007 Dec 10
4
Mongrel and http 1.1 OPTIONS keyword
Hello.
I just seen some errors in my mongrel application log:
It seems related to the httpd OPTIONS keyword
Example:
Processing LoginController#login (for .30.5.208 at 2007-12-10 09:00:23)
[OPTIONS]
and our ruby application does not know what to do with it. and finally
send an error
Does mongrel (which is the http server) is supposed to deal with these
kind of request ?
I think these
2006 Apr 04
1
Mongrel Web Server 0.3.12.1 -- Iron Mongrel
Hello All Mongrel Users,
For the unintiated, Mongrel is a web server that runs Ruby web applications
really fast. Read http://mongrel.rubyforge.org/ to get find out more about
it.
This is the Iron Mongrel release. It is the result of trying to trash
Mongrel until it can''t move and then fixing anything that comes up. The
work was done on EastMedia''s and VeriSign''s
2007 Sep 22
2
http helpers c extension
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)
2006 May 14
0
[UPDATE] Mongrel 0.3.13 Pre-Release -- Conditional Responses, Better Parsing
Hi Folks,
As you can tell we''re getting closer to the 0.3.13 release being
official. There''s a new pre-release available for non-win32 users:
gem install mongrel --source=http://mongrel.rubyforge.org/releases/
Which has the following fixes and enhancements:
* Rewritten internal HTTP processing to protect against trickle
attacks. This means that a client can send one byte
2019 Sep 18
0
CESA-2019:2258 Moderate CentOS 7 http-parser Security Update
CentOS Errata and Security Advisory 2019:2258 Moderate
Upstream details at : https://access.redhat.com/errata/RHSA-2019:2258
The following updated files have been uploaded and are currently
syncing to the mirrors: ( sha256sum Filename )
x86_64:
1ec6d7fad1b3e6ee8d32ffedcce19bcc69fd3ad7479dee7fda7c8a529209b91c http-parser-2.7.1-8.el7.i686.rpm
2020 Mar 04
0
CESA-2020:0703 Important CentOS 7 http-parser Security Update
CentOS Errata and Security Advisory 2020:0703 Important
Upstream details at : https://access.redhat.com/errata/RHSA-2020:0703
The following updated files have been uploaded and are currently
syncing to the mirrors: ( sha256sum Filename )
x86_64:
18c1947137ff700a633b90f89d11594fe0e7a286c25eba5a11624b19f5d0d8e2 http-parser-2.7.1-8.el7_7.2.i686.rpm
2006 Aug 20
14
http parser
Just thought I''d let you know that your http parser worked great for
creating an http protocol handler for Eventmachine. It wouldn''t take
that much effort to use Eventmachine for Mongrel, might be worth a
shot just to see how it does. A few things would need to be
restructered, like HttpRequest where you read the rest of the body,
and calling the handler. But it
2007 Nov 10
1
Upgrade on windows to 1.1
Attempting remote update of mongrel
Select which gem to install for your platform (i386-mswin32)
1. mongrel 1.1 (java)
2. mongrel 1.1 (mswin32)
3. mongrel 1.1 (ruby)
4. mongrel 1.0.4 (ruby)
5. mongrel 1.0.4 (mswin32)
6. Skip this gem
7. Cancel installation
2
> ERROR: While executing gem ... (OpenURI::HTTPError)
404 Not Found
This is using the NetBean IDE''s ''ruby
2008 Jun 01
3
rbx gem
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
2006 Aug 24
10
Invalid HTTP format, parsing fails
Hi,
I am having a bit of a problem with my app that is using mongrel.
For a particular vendor we use, they are generating links that look like:
2008 Sep 16
1
another assertion failure in current 1.1 hg (1.1.3 was working fine) - file message-address.c: line 43 (parse_local_part): assertion failed: (ctx->parser.data != ctx->parser.end)
file message-address.c: line 43 (parse_local_part): assertion failed:
(ctx->parser.data != ctx->parser.end)
#0 0x001b3402 in __kernel_vsyscall ()
No symbol table info available.
#1 0x0043ed20 in raise () from /lib/libc.so.6
No symbol table info available.
#2 0x00440631 in abort () from /lib/libc.so.6
No symbol table info available.
#3 0x080f6968 in default_fatal_finish