kytv/I2P_Website
1
0
Fork 0
forked from I2P_Developers/i2p.www
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

More old path updates

Browse Source
This commit is contained in:
str4d
2013-12-30 05:50:05 +00:00
parent b6cd001ce1
commit 29ed31e401
2 changed files with 12 additions and 12 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
i2p2www/pages/site/docs/index.html
View File

@@ -236,7 +236,7 @@ Traditionally used only by Java applications and higher-level APIs.
</li><li>
<a href="{{ site_url('get-involved/todo') }}">{{ _('To Do List') }}</a> ({{ _('not current') }})
</li><li>
<a href="invisiblenet.html">Ancient invisiblenet I2P documents</a> (2003)
<a href="{{ site_url('misc/invisiblenet') }}">Ancient invisiblenet I2P documents</a> (2003)
</li></ul>

22
i2p2www/pages/site/docs/spec/i2cp.html
View File

@@ -527,7 +527,7 @@ If the Date in the Session Config is too far (more than +/- 30 seconds) from the
</li><li>
If there is already a session on the router for this Destination, the session will be rejected.
</li><li>
The <a href="common_structures_spec#type_Mapping">Mapping</a> in the Session Config
The <a href="{{ site_url('docs/spec/common-structures') }}#type_Mapping">Mapping</a> in the Session Config
must be sorted by key so that the signature will be validated correctly in the router.
</li></ul>
@@ -661,7 +661,7 @@ This is only useful if the client and router are not in the same JVM.
If it is not present, the client is version 0.8.6 or earlier.
</li><li>
Preliminary: As of release 0.9.10, the authentication
<a href="common_structures_spec#type_Mapping">Mapping</a>
<a href="{{ site_url('docs/spec/common-structures') }}#type_Mapping">Mapping</a>
may be included, with the keys i2cp.username and i2cp.password.
The Mapping need not be sorted as this message is not signed.
Prior to and including 0.9.10, authentication is included in the
@@ -692,15 +692,15 @@ which is much more efficient.
<h4>Contents</h4>
<ol><li>
4 byte <a href="common_structures_spec#type_Integer">Integer</a> request ID
4 byte <a href="{{ site_url('docs/spec/common-structures') }}#type_Integer">Integer</a> request ID
</li><li>
4 byte <a href="common_structures_spec#type_Integer">Integer</a> timeout (ms)
4 byte <a href="{{ site_url('docs/spec/common-structures') }}#type_Integer">Integer</a> timeout (ms)
</li><li>
1 byte <a href="common_structures_spec#type_Integer">Integer</a> request type
1 byte <a href="{{ site_url('docs/spec/common-structures') }}#type_Integer">Integer</a> request type
</li><li>
<a href="common_structures_spec#struct_Hash">SHA-256 Hash</a>
<a href="{{ site_url('docs/spec/common-structures') }}#struct_Hash">SHA-256 Hash</a>
or
host name <a href="common_structures_spec#struct_String">String</a>
host name <a href="{{ site_url('docs/spec/common-structures') }}#struct_String">String</a>
</li></ol>
<h4>Notes</h4>
@@ -730,11 +730,11 @@ Sent from Router to Client in response to a
</p>
<h4>Contents</h4>
<ol><li>
4 byte <a href="common_structures_spec#type_Integer">Integer</a> request ID
4 byte <a href="{{ site_url('docs/spec/common-structures') }}#type_Integer">Integer</a> request ID
</li><li>
1 byte <a href="common_structures_spec#type_Integer">Integer</a> result code
1 byte <a href="{{ site_url('docs/spec/common-structures') }}#type_Integer">Integer</a> result code
</li><li>
<a href="common_structures_spec#struct_Destination">Destination</a>,
<a href="{{ site_url('docs/spec/common-structures') }}#struct_Destination">Destination</a>,
only present if result code is zero.
</li></ol>
@@ -954,7 +954,7 @@ As of release 0.7.1.
</li><li>
If the Date in the Session Config is too far (more than +/- 30 seconds) from the router's current time, the session will be rejected.
</li><li>
The <a href="common_structures_spec#type_Mapping">Mapping</a> in the Session Config
The <a href="{{ site_url('docs/spec/common-structures') }}#type_Mapping">Mapping</a> in the Session Config
must be sorted by key so that the signature will be validated correctly in the router.
</li></ul>