mirror of
https://github.com/Grasscutters/mitmproxy.git
synced 2024-11-27 02:24:18 +00:00
http2: update docs
This commit is contained in:
parent
46255e6e9c
commit
5c0f0c2c22
@ -1,47 +1,23 @@
|
||||
|
||||
<pre class="example">method:path:[colon-separated list of features]</pre></p>
|
||||
<pre class="example">method:path:[colon-separated list of features]</pre>
|
||||
</p>
|
||||
|
||||
<table class="table table-bordered">
|
||||
<tbody>
|
||||
|
||||
<tr>
|
||||
<td>method</td>
|
||||
<td>
|
||||
<p>
|
||||
A <a href="#valuespec">VALUE</a> specifying the HTTP method to use. Standard
|
||||
methods do not need to be enclosed in quotes, while non-standard methods
|
||||
can be specified as quoted strings.
|
||||
</p>
|
||||
|
||||
<p>A <a href="#valuespec">VALUE</a> specifying the HTTP
|
||||
method to use. Standard methods do not need to be
|
||||
enclosed in quotes, while non-standard methods can be
|
||||
specified as quoted strings.</p>
|
||||
|
||||
<p>The special method <b>ws</b> creates a valid
|
||||
websocket upgrade GET request, and signals to pathoc to
|
||||
switch to websocket recieve mode if the server responds
|
||||
correctly. Apart from that, websocket requests are just
|
||||
like any other, and all aspects of the request can be
|
||||
over-ridden.</p>
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td> b<a href="#valuespec">VALUE</a> </td>
|
||||
<td>
|
||||
Set the body. The appropriate Content-Length header is
|
||||
added automatically unless the "r" flag is set.
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td> c<a href="#valuespec">VALUE</a> </td>
|
||||
<td>
|
||||
A shortcut for setting the Content-Type header. Equivalent to
|
||||
h"Content-Type"=VALUE
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td> d<a href="#offsetspec">OFFSET</a> </td>
|
||||
<td>
|
||||
Disconnect after OFFSET bytes.
|
||||
<p>
|
||||
The special method <b>ws</b> creates a valid websocket upgrade GET
|
||||
request, and signals to pathoc to switch to websocket recieve mode
|
||||
if the server responds correctly. Apart from that, websocket requests
|
||||
are just like any other, and all aspects of the request can be over-ridden.
|
||||
</p>
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
@ -52,45 +28,29 @@
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td> i<a href="#offsetspec">OFFSET</a>,<a href="#valuespec">VALUE</a> </td>
|
||||
<td>
|
||||
Inject the specified value at the offset.
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td> p<a href="#offsetspec">OFFSET</a>,SECONDS </td>
|
||||
<td>
|
||||
Pause for SECONDS seconds after OFFSET bytes. SECONDS can
|
||||
be an integer or "f" to pause forever.
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>r</td>
|
||||
<td>
|
||||
Set the "raw" flag on this response. Pathod will not
|
||||
calculate a Content-Length header if a body is set.
|
||||
Set the "raw" flag on this response. Pathod will not calculate a Content-Length header
|
||||
if a body is set.
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td> s<a href="#valuespec">VALUE</a> </td>
|
||||
<td>c<a href="#valuespec">VALUE</a></td>
|
||||
<td>
|
||||
An embedded Response specification, appended to the path
|
||||
of the request.
|
||||
A shortcut for setting the Content-Type header. Equivalent to h"Content-Type"=VALUE
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td> u<a href="#valuespec">VALUE</a> <br> uSHORTCUT </td>
|
||||
<td>u<a href="#valuespec">VALUE</a>
|
||||
<br> uSHORTCUT
|
||||
</td>
|
||||
|
||||
<td>
|
||||
|
||||
Set a User-Agent header on this request. You can
|
||||
specify either a complete <a
|
||||
href="#valuespec">VALUE</a>, or a User-Agent shortcut:
|
||||
Set a User-Agent header on this request. You can specify either a complete
|
||||
<a href="#valuespec">VALUE</a>, or a User-Agent shortcut:
|
||||
|
||||
<table class="table table-condensed">
|
||||
{% for i in uastrings %}
|
||||
@ -100,7 +60,21 @@
|
||||
</tr>
|
||||
{% endfor %}
|
||||
</table>
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>b<a href="#valuespec">VALUE</a></td>
|
||||
<td>
|
||||
Set the body. The appropriate Content-Length header is added automatically unless the
|
||||
"r" flag is set.
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>s<a href="#valuespec">VALUE</a></td>
|
||||
<td>
|
||||
An embedded Response specification, appended to the path of the request.
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
@ -110,5 +84,30 @@
|
||||
Repeat this message N times.
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>d<a href="#offsetspec">OFFSET</a></td>
|
||||
<td>
|
||||
<span class="badge badge-info">HTTP/1 only</span>
|
||||
Disconnect after OFFSET bytes.
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>i<a href="#offsetspec">OFFSET</a>,<a href="#valuespec">VALUE</a></td>
|
||||
<td>
|
||||
<span class="badge badge-info">HTTP/1 only</span>
|
||||
Inject the specified value at the offset.
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>p<a href="#offsetspec">OFFSET</a>,SECONDS</td>
|
||||
<td>
|
||||
<span class="badge badge-info">HTTP/1 only</span>
|
||||
Pause for SECONDS seconds after OFFSET bytes. SECONDS can be an integer or "f" to pause
|
||||
forever.
|
||||
</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
@ -1,5 +1,4 @@
|
||||
|
||||
<pre class="example">code:[colon-separated list of features]</pre></p>
|
||||
<pre class="example">code:[colon-separated list of features]</pre>
|
||||
|
||||
<table class="table table-bordered">
|
||||
<tbody>
|
||||
@ -7,35 +6,20 @@
|
||||
<td>code</td>
|
||||
<td>
|
||||
<p>An integer specifying the HTTP response code.</p>
|
||||
|
||||
<p>The special method <b>ws</b> creates a valid
|
||||
websocket upgrade response (code 101), and moves pathod
|
||||
to websocket mode. Apart from that, websocket responses
|
||||
are just like any other, and all aspects of the
|
||||
response can be over-ridden.</p>
|
||||
<p>
|
||||
The special method <b>ws</b> creates a valid websocket upgrade response
|
||||
(code 101), and moves pathod to websocket mode. Apart from that, websocket
|
||||
responses are just like any other, and all aspects of the response
|
||||
can be over-ridden.
|
||||
</p>
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td> b<a href="#valuespec">VALUE</a> </td>
|
||||
<td>m<a href="#valuespec">VALUE</a></td>
|
||||
<td>
|
||||
Set the body. The appropriate Content-Length header is
|
||||
added automatically unless the "r" flag is set.
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td> c<a href="#valuespec">VALUE</a> </td>
|
||||
<td>
|
||||
A shortcut for setting the Content-Type header. Equivalent to
|
||||
h"Content-Type"=VALUE
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td> d<a href="#offsetspec">OFFSET</a> </td>
|
||||
<td>
|
||||
Disconnect after OFFSET bytes.
|
||||
<span class="badge badge-info">HTTP/1 only</span>
|
||||
HTTP Reason message. Automatically chosen according to the response code if not specified.
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
@ -46,44 +30,58 @@
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
|
||||
<tr>
|
||||
<td> i<a href="#offsetspec">OFFSET</a>,<a href="#valuespec">VALUE</a> </td>
|
||||
<td>r</td>
|
||||
<td>
|
||||
Inject the specified value at the offset.
|
||||
Set the "raw" flag on this response. Pathod will not calculate a Content-Length header
|
||||
if a body is set, or add a Date header to the response.
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>l<a href="#valuespec">VALUE</a></td>
|
||||
<td>
|
||||
A shortcut for setting the Location header. Equivalent to
|
||||
h"Location"=VALUE
|
||||
A shortcut for setting the Location header. Equivalent to h"Location"=VALUE
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td> m<a href="#valuespec">VALUE</a> </td>
|
||||
<td>c<a href="#valuespec">VALUE</a></td>
|
||||
<td>
|
||||
HTTP Reason message. Automatically chosen according to
|
||||
the response code if not specified.
|
||||
A shortcut for setting the Content-Type header. Equivalent to h"Content-Type"=VALUE
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>b<a href="#valuespec">VALUE</a></td>
|
||||
<td>
|
||||
Set the body. The appropriate Content-Length header is added automatically unless the
|
||||
"r" flag is set.
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>d<a href="#offsetspec">OFFSET</a></td>
|
||||
<td>
|
||||
<span class="badge badge-info">HTTP/1 only</span>
|
||||
Disconnect after OFFSET bytes.
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>i<a href="#offsetspec">OFFSET</a>,<a href="#valuespec">VALUE</a></td>
|
||||
<td>
|
||||
<span class="badge badge-info">HTTP/1 only</span>
|
||||
Inject the specified value at the offset.
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>p<a href="#offsetspec">OFFSET</a>,SECONDS</td>
|
||||
<td>
|
||||
Pause for SECONDS seconds after OFFSET bytes. SECONDS can
|
||||
be an integer or "f" to pause forever.
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td> r </td>
|
||||
<td>
|
||||
Set the "raw" flag on this response. Pathod will not
|
||||
calculate a Content-Length header if a body is set, or add
|
||||
a Date header to the response.
|
||||
<span class="badge badge-info">HTTP/1 only</span>
|
||||
Pause for SECONDS seconds after OFFSET bytes. SECONDS can be an integer or "f" to pause
|
||||
forever.
|
||||
</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
|
Loading…
Reference in New Issue
Block a user