summaryrefslogtreecommitdiffstats
path: root/docs/manual/mod/mod_http2.xml
diff options
context:
space:
mode:
Diffstat (limited to 'docs/manual/mod/mod_http2.xml')
-rw-r--r--docs/manual/mod/mod_http2.xml10
1 files changed, 5 insertions, 5 deletions
diff --git a/docs/manual/mod/mod_http2.xml b/docs/manual/mod/mod_http2.xml
index f4a17dc03e..1648eb73ef 100644
--- a/docs/manual/mod/mod_http2.xml
+++ b/docs/manual/mod/mod_http2.xml
@@ -267,15 +267,15 @@
</p>
<example><title>Before Priority Rule</title>
<highlight language="config">
- H2PushPriority application/json Before 256
+ H2PushPriority application/json Before
</highlight>
</example>
<p>
This says that any pushed stream of content type 'application/json'
should be send out <em>before</em> X. This makes P1 dependent
on Y and X dependent on P1. So, X will be stalled as long as
- P1 has data to send. The effective weight is calculated as
- in the interleaved case.
+ P1 has data to send. The effective weight is inherited from the
+ client stream. Specifying a weight is not allowed.
</p>
<p>
Be aware that the effect of priority specifications is limited
@@ -291,13 +291,13 @@
<li>'*' is the only special content-type that matches all others.
'image/*' will not work.</li>
<li>The default dependency is 'After'. </li>
- <li>There are also default weights: for 'After' it is 16, otherwise 256.
+ <li>There are also default weights: for 'After' it is 16, 'interleaved' is 256.
</li>
</ol>
<example><title>Shorter Priority Rules</title>
<highlight language="config">
H2PushPriority application/json 32 # an After rule
-H2PushPriority image/jpeg before # weight 256 default
+H2PushPriority image/jpeg before # weight inherited
H2PushPriority text/css interleaved # weight 256 default
</highlight>
</example>