forked from I2P_Developers/i2p.www
Seems jinja2 don't allow us to use function names in template values.
This commit is contained in:
@@ -230,13 +230,15 @@ It is advertised with an extension message, identified as "i2p_dht" in
|
||||
It contains a bencoded dictionary with two keys, "port" and "rport", both integers.
|
||||
{%- endtrans %}</p>
|
||||
|
||||
{% set i2cp_pages = site_url('docs/protocol/i2cp') %}
|
||||
|
||||
<p>{% trans -%}
|
||||
The UDP (datagram) port listed in the compact node info is used
|
||||
to receive repliable (signed) datagrams.
|
||||
This is used for queries, except for announces.
|
||||
We call this the "query port".
|
||||
This is the "port" value from the extension message.
|
||||
Queries use <a href="{{ site_url('docs/protocol/i2cp') }}">I2CP</a>
|
||||
Queries use <a href="{{ i2cp_pages }}">I2CP</a>
|
||||
protocol number 17.
|
||||
{%- endtrans %}</p>
|
||||
|
||||
@@ -249,7 +251,7 @@ contain tokens sent in the query, and need not be signed.
|
||||
We call this the "response port".
|
||||
This is the "rport" value from the extension message.
|
||||
It must be 1 + the query port.
|
||||
Responses and announces use <a href="{{ site_url('docs/protocol/i2cp') }}">I2CP</a>
|
||||
Responses and announces use <a href="{{ i2cp_pages }}">I2CP</a>
|
||||
protocol number 18.
|
||||
{%- endtrans %}</p>
|
||||
|
||||
|
Reference in New Issue
Block a user