From 424d15c28ba46d2d42b96d2247166eb13b4c7b8e Mon Sep 17 00:00:00 2001 From: Aldo Cortesi Date: Wed, 26 Sep 2012 11:21:40 +1200 Subject: [PATCH] Expand the docs to explain pathoc multiple requests. --- libpathod/templates/docs_pathoc.html | 37 ++++++++++++++++++++++++++++ 1 file changed, 37 insertions(+) diff --git a/libpathod/templates/docs_pathoc.html b/libpathod/templates/docs_pathoc.html index e1bef4d5a..5c07aee33 100644 --- a/libpathod/templates/docs_pathoc.html +++ b/libpathod/templates/docs_pathoc.html @@ -43,6 +43,43 @@ the command-line help:

+
+
+

Multiple Requests

+
+ +

There are two ways to tell pathoc to issue multiple requests. The first + is to specify them on the command-line, like so:

+ + 
> pathoc google.com get:/ get:/
+<< 301 Moved Permanently: 219 bytes
+<< 301 Moved Permanently: 219 bytes
+ +

In this case, pathoc issues the specified requests over the same TCP + connection - so in the above example only one connection is made to + google.com

+ +

The other way to issue multiple requets is to use the -n flag:

+ + 
> pathoc -n 2 google.com get:/
+<< 301 Moved Permanently: 219 bytes
+<< 301 Moved Permanently: 219 bytes
+ +

The output is identical, but two separate TCP connections are made to + the upstream server. These two specification styles can be combined:

+ + 
> pathoc -n 2 google.com get:/ get:/
+<< 301 Moved Permanently: 219 bytes
+<< 301 Moved Permanently: 219 bytes
+<< 301 Moved Permanently: 219 bytes
+<< 301 Moved Permanently: 219 bytes
+ +

Here, two distinct TCP connections are made, with two requests issued + over each.

+ +
+ +

Basic Fuzzing