doc/rdoc/files/README.html in rfuzz-0.6 vs doc/rdoc/files/README.html in rfuzz-0.7
- old
+ new
@@ -54,11 +54,11 @@
<td>README
</td>
</tr>
<tr class="top-aligned-row">
<td><strong>Last Update:</strong></td>
- <td>Wed Jul 19 17:15:09 EDT 2006</td>
+ <td>Wed Jul 19 15:02:32 PDT 2006</td>
</tr>
</table>
</div>
<!-- banner header -->
@@ -78,15 +78,21 @@
</p>
<p>
At the moment is has a working and fairly extensive HTTP 1.1 client and
some basic statistics math borrowed from the Mongrel project.
</p>
+<h2>RubyForge Project</h2>
<p>
-In order for the test cases to run you need to start any Rails project on
-port 3000. Future releases will have tests starting built-in Mongrel
-servers to validate client functionality.
+The project is hosted at:
</p>
+<pre>
+ http://rubyforge.org/projects/rfuzz/
+</pre>
+<p>
+Where you can file bugs and other things, as well as download gems
+manually.
+</p>
<h2>Motivation</h2>
<p>
The motivation for <a href="../classes/RFuzz.html">RFuzz</a> comes from
little scripts I’ve written during Mongrel development to
"fuzz" or attack the Mongrel code.
@@ -100,22 +106,22 @@
<p>
It may also perform analysis of performance data and work as a simply load
or pen testing tool. This is only a secondary goal though since
there’s plenty of good tools for that.
</p>
-<h2>Downloading</h2>
+<h2>Installing</h2>
<p>
-Right now <a href="../classes/RFuzz.html">RFuzz</a> just sits on my server,
-so you can download <a
-href="http://www.zedshaw.com/projects/rfuzz/rfuzz-0.4.gem">www.zedshaw.com/projects/rfuzz/rfuzz-0.4.gem</a>
-or <a
-href="http://www.zedshaw.com/projects/rfuzz/rfuzz-0.4.tgz">www.zedshaw.com/projects/rfuzz/rfuzz-0.4.tgz</a>
-for the 0.4 version.
+You can install <a href="../classes/RFuzz.html">RFuzz</a> by simply using
+RubyGems:
</p>
+<pre>
+ sudo gem install rfuzz
+</pre>
<p>
-Once it can actually be used to fuzz a system I’ll make a RubyForge
-project.
+It doesn’t support windows unless you have build tools that can
+compile modules against Ruby. No, you don’t get this with Ruby One
+Click.
</p>
<h2><a href="../classes/RFuzz.html">RFuzz</a> HTTP Client</h2>
<p>
It also comes from not being satisfied with the stock net/http library.
While this library is good for high-level HTTP access to resources, it is
@@ -186,15 +192,14 @@
overrides the parameters. This makes it possible to set common parameters,
cookies, and headers in blocks of requests to reduce repetition.
</p>
<h3>Client Limitations</h3>
<p>
-You can use the HTTP client right now to do HTTP requests and it is
-probably a lot easier than net/http for most requests that don’t
-require complex POST bodies encoding. It also contains full documentation
-and has a full suite of encoding and decoding libraries. It can’t
-handle large HTTP bodies yet.
+The client handles chunked encoding inside the parser but the code for it
+is still quite nasty. I’ll be attacking that and cleaning it up very
+soon. Even with this it’s able to efficiently parse chunked encodings
+without many problems (but could be better).
</p>
<p>
It can’t also parse cookies properly yet, so the above example kind
of works, but the cookie isn’t returned right.
</p>
@@ -424,15 +429,9 @@
was just done at the wrong time or in the wrong situation. If you just ran
a test once with the same settings every time you might not find out until
later that there was some confounding element which made the test invalid.
</p>
<h2>Source Code</h2>
-<p>
-The .tgz file (mentioned Downloading) has the source if you’re
-interested. Remember that *you must have a rails app on 3000* for the tests
-to run. Just a limitation right now until I hook Mongrel into the test
-framework as the feedback loop.
-</p>
<p>
You can also view <a
href="http://www.zedshaw.com/projects/rfuzz/coverage">www.zedshaw.com/projects/rfuzz/coverage</a>/
for the rcov generated coverage report which is also a decent source
browser.
\ No newline at end of file