about summary refs log tree commit homepage
DateCommit message (Collapse)
2009-09-02clogger 0.0.4 v0.0.4
2009-09-01correctly rebuild simple HTTP/0.9 GET requests
Back in HTTP/0.9 days (before it was called HTTP/0.9), "GET /uri/goes/here\r\n" was a valid HTTP request. See rfc 1945, section 4.1 for details on this ancient "Simple-Request" scheme used by HTTP/0.9 clients.
2009-09-01README: point to repo.or.cz git mirror setup
The rubyforge one is out-of-date right now, so lets stop referencing it until the issues around it can be fixed.
2009-09-01README: new git repository
I seem to have problems pushing to Rubyforge at the moment, so I'll put the repository on a host I have more control over. Tracking the issue here: http://rubyforge.org/tracker/index.php?func=detail&aid=26185&group_id=5&atid=102
2009-09-01Ensure hex escaping is done in uppercase
The pure variant was using lower-case output instead of upper case, the ext variant was actually fine in this case. This is for nginx output format compatibility.
2009-09-01ext: ensure headers#each in response is valid
We're not Rack::Lint, but we still need to take steps to avoid segfaulting if we host non-Rack::Lint-compliant applications. This also updates the pure variant to fail on bad applications, too.
2009-09-01ext: compiler compatibility fix
Remove trailing "," for enum
2009-09-01GNUmakefile: post_news after release
2009-08-29clogger 0.0.3 v0.0.3
2009-08-29Merge dcvr:clogger
* dcvr:clogger: ext: several cleanups and robustness improvements ext: explicitly gc_mark each struct element
2009-08-29ext: several cleanups and robustness improvements
Add a little more tolerance for bad applications that may not give us string objects. This should only have a minor performance penalty for proper applications but at least ensures we don't segfault on misbehaving apps.
2009-08-29ext: explicitly gc_mark each struct element
rb_gc_mark_locations doesn't seem in common use for structs and there was a fencepost error so the response element didn't seem to be marked at times. This should fix random errors I've been seeing on big/longer response bodies.
2009-08-29GNUmakefile: fix "release" now that I've used it..
* pass correct arguments for changes * correctly generate change log from git * add blank line after description in release notes
2009-08-29clogger 0.0.2 v0.0.2
2009-08-29Log bad/invalid app responses as 500 errors
Some misbehaved apps can do this to us, and we don't want the C extension to segfault when this happens.
2009-08-29support "$request_uri" as a log variable
This was documented in the README but never implemented. Some popular web servers set REQUEST_URI even though it's not required by Rack, so allow this variable to be used if possible. As a side effect, it is also less likely to be modified by certain handlers (*cough*Rails::Rack::Static*cough*).
2009-08-29GNUmakefile: "release" steps
2009-08-28Remove benchmarks from Manifest.txt v0.0.1
We don't care
2009-08-28README: updates and clarifications
2009-08-28initial import