I2P_Developers/i2p.www
3
0
Fork 5
Code Issues 27 Pull Requests Actions 1 Packages Projects Releases Wiki Activity

SAM 3.2: Clarifications

Browse Source 
SSU: Notes on RelayRequest
This commit is contained in:
zzz
2015-12-01 21:36:12 +00:00
parent 4a5f417072
commit be71dd75d8
2 changed files with 5 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
i2p2www/pages/site/docs/api/samv3.html
View File

@@ -94,11 +94,13 @@ The following changes will be incorporated in the main part of this document soo
<li>The server's control socket may optionally offer SSL/TLS support, as configured on the server and client.
Implementations may offer other transport layers as well; this is outside the scope of the protocol definition.
<li>For STREAM FORWARD, client may add SSL=true to use an SSL socket
<li>New commands QUIT, STOP and EXIT will close the session and socket
<li>New commands QUIT, STOP and EXIT will close the session and socket. Implementation is optional,
for ease in testing via telnet.
<li>Command parsing will properly handle UTF-8
<li>Command parsing reliably handles whitespace inside quotes
<li>A backslash '\' may escape quotes on the command line
<li>It is recommended but not required that the server map commands and option names to upper case.
<li>It is recommended but not required that the server map commands to upper case, for ease in testing via telnet.
Do not map keys to upper case, as this would corrupt I2CP options.
<li>Empty option values such as PROTOCOL or PROTOCOL= may be allowed, implementation dependent.
<li>Servers may implement timeouts for the HELLO or subsequent commands, implementation dependent.
</ul>