UPDATE: Info about rewinding the InputStream has been re-addressed here.
Version 2.0 is well on it's way. I've run into a small snag with the way the HttpModule stalls spam requests... and I'll keep working on that as time allows. Otherwise version 2.0 is looking sweet. It's got TONS less functionality, and works tons better (there was too much functionality in Version 1.0 - and to date, i don't know that anyone has used any of it. All of the SPAM BLOCKING functionality remains the focus for Version 2.0).
Anywho, Version 1.2 has just been uploaded to the downloads page.
Ayende Rahien was kind enough to work with me through a problem he was having with ReverseDOS breaking his blogger-API interaction. He kept thinking it was a problem with ReverseDOS not rewinding the Request.InputStream correctly. I said... phhhhwww to that. Until it became abundantly clear that that WAS the problem.
See, in the 1.1 fix I just rewound the InputStream BEFORE each post filter looked at it. When the post filter was done looking at it, the stream was still left wound-out. The new code looks like:
string output;
using(StreamReader sr = new StreamReader(request.InputStream))
output = sr.ReadToEnd();
// rewind for neighbors (including subsequent post filters)
request.InputStream.Seek(0, SeekOrigin.Begin);
That will leave the stream 're-wound' for subsequent interactions (and since each filter rewinds after it's done scanning, logic would dictate that it will always be rewound when a filter gets ahold of it -- assuming other apps out there have good playground etiquette). Thanks a ton for your patience and help Ayende!
(Keep an eye out for the 2.0 announcement... )
Those of you
that know me, know that I'm usually 
