forked from I2P_Developers/i2p.www
Update note about i2pd support of b32 addresses in SAM
This commit is contained in:
@@ -1,7 +1,7 @@
|
||||
{% extends "global/layout.html" %}
|
||||
{% block title %}SAM V3{% endblock %}
|
||||
{% block lastupdated %}2021-03{% endblock %}
|
||||
{% block accuratefor %}0.9.49{% endblock %}
|
||||
{% block lastupdated %}2021-04{% endblock %}
|
||||
{% block accuratefor %}0.9.50{% endblock %}
|
||||
{% block content %}
|
||||
<p>SAM is a simple client protocol for interacting with I2P.
|
||||
SAM is the recommended protocol for non-Java applications to connect to the I2P network,
|
||||
@@ -671,7 +671,7 @@ depending on signature type.
|
||||
<b>NOTE:</b>
|
||||
Since about 2014 (SAM v3.1), Java I2P has also supported hostnames and b32 addresses for the $destination, but this was previously undocumented.
|
||||
Hostnames and b32 addresses are now officially supported by Java I2P as of release 0.9.48.
|
||||
The i2pd router does not currently support hostnames and b32 addresses; support may be added in a future release.
|
||||
The i2pd router has always supported hostnames. I2pd supports b32 addresses as of release 2.38.0 (0.9.50).
|
||||
</p>
|
||||
|
||||
<h4>Connect Response</h4>
|
||||
|
Reference in New Issue
Block a user