Grasscutters/mitmproxy
3
0
Fork 0
mirror of https://github.com/Grasscutters/mitmproxy.git synced 2024-11-27 10:26:23 +00:00
Code Issues Projects Releases Wiki Activity

docs: pathod

Browse Source
This commit is contained in:
Aldo Cortesi 2012-07-30 00:14:34 +12:00
parent bc1cfd9f75
commit b1ac4245c8
1 changed files with 17 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

26
libpathod/templates/docs_pathod.html
View File

@ -33,18 +33,17 @@ this, just fire up your browser, and point it to the following URL:</p>
<pre class="example">http://localhost:9999</pre> <pre class="example">http://localhost:9999</pre>
<p>The default crafting anchor point is the path <b>/p/</b>. Anything after <p>The default crafting anchor point is the path <b>/p/</b>. Anything after
this URL prefix is treated as a response specifier. Hitting the following URL this URL prefix is treated as a response specifier. So, hitting the following
will generate an HTTP 200 response with 100 bytes of random data:</p> URL will generate an HTTP 200 response with 100 bytes of random data:</p>
<pre class="example">http://localhost:9999/p/200:b@100</pre> <pre class="example">http://localhost:9999/p/200:b@100</pre>
<p>See the <a href="/docs/language">language documentation</a> to get (much) <p>See the <a href="/docs/language">language documentation</a> to get (much)
fancier. The pathod daemon also takes a number of configuration options. To fancier. The pathod daemon also takes a range of configuration options. To view
view those, use the command-line help:</p> those, use the command-line help:</p>
<pre class="terminal">./pathod --help</pre> <pre class="terminal">./pathod --help</pre>
</section> </section>
@ -53,13 +52,15 @@ view those, use the command-line help:</p>
<h1>Anchors</h1> <h1>Anchors</h1>
</div> </div>
You can also add anchors to the pathod server that serve a fixed response <p>Anchors provide an alternative to specifying the response in the URL.
whenever a matching URL is requested:</p> Instead, you attach a response to a pre-configured anchor point, specified with
a regex. When a URL matching the regex is requested, the specified response is
served.</p>
<pre class="terminal">./pathod -a "/foo=200"</pre> <pre class="terminal">./pathod -a "/foo=200"</pre>
<p>Here, "/foo" a regex specifying the anchor path, and the part after the "=" is <p>Here, "/foo" is ithe regex specifying the anchor path, and the part after
a response specifier.</p> the "=" is a response specifier.</p>
</section> </section>
@ -69,6 +70,13 @@ a response specifier.</p>
<h1>File Access</h1> <h1>File Access</h1>
</div> </div>
<p>There are two operators in the <a href="/docs/language">language</a> that
load contents from file - the <b>+</b> operator to load an entire request
specification from file, and the <b>&gt;</b> value specifier. In pathod, both
of these operators are restricted to a directory specified at startup, or
disabled if no directory is specified:</p>
<pre class="terminal">./pathod -d ~/staticdir"</pre>
</section> </section>