diff --git a/i2p2www/pages/site/docs/api/i2ptunnel.html b/i2p2www/pages/site/docs/api/i2ptunnel.html
index c8a81527..504eaf9e 100644
--- a/i2p2www/pages/site/docs/api/i2ptunnel.html
+++ b/i2p2www/pages/site/docs/api/i2ptunnel.html
@@ -1,7 +1,7 @@
{% extends "global/layout.html" %}
{% block title %}I2PTunnel{% endblock %}
-{% block lastupdated %}January 2016{% endblock %}
-{% block accuratefor %}0.9.24{% endblock %}
+{% block lastupdated %}2022-09{% endblock %}
+{% block accuratefor %}1.9.0{% endblock %}
{% block content %}
{% trans %}Overview{% endtrans %}
@@ -35,10 +35,9 @@ A HTTP proxy used for browsing I2P and the regular internet anonymously through
Browsing internet through I2P uses a random proxy specified by the "Outproxies:" option.
{%- endtrans %}
Irc2P - localhost:6668 - {% trans %}An IRC tunnel to the default anonymous IRC network, Irc2P.{% endtrans %}
-mtn.i2p2.i2p - localhost:8998 - {% trans monotone='http://en.wikipedia.org/wiki/Monotone_%28software%29' -%}
-The anonymous monotone
-sourcecode repository for I2P
-{%- endtrans %}
+gitssh.idk.i2p - localhost:7670 -
+SSH access to the project Git repository
+
smtp.postman.i2p - localhost:7659 - {% trans postman=i2pconv('hq.postman.i2p') -%}
A SMTP service provided by postman at {{ postman }}
{%- endtrans %}
@@ -73,6 +72,50 @@ in a HTTP request. Supports proxying onto internet if an outproxy is provided. S
From:
+
+The HTTP client proxy provides a number of services to protect the user
+and to provide a better user experience.
+
+
+- Request header processing:
+
- Strip privacy-problematic headers
+
- Routing to local or remote outproxy
+
- Outproxy selection, caching, and reachability tracking
+
- Hostname to destination lookups
+
- Host header replacement to b32
+
- Add header to indicate support for transparent decompression
+
- Force connection: close
+
- RFC-compliant proxy support
+
- RFC-compliant hop-by-hop header processing and stripping
+
- Optional digest and basic username/password authentication
+
- Optional outproxy digest and basic username/password authentication
+
- Buffering of all headers before passing through for efficiency
+
- Jump server links
+
- Jump response processing and forms (address helper)
+
- Blinded b32 processing and credential forms
+
- Supports standard HTTP and HTTPS (CONNECT) requests
+
+
+ - Response header processing:
+
- Check for whether to decompress response
+
- Force connection: close
+
- RFC-compliant hop-by-hop header processing and stripping
+
- Buffering of all headers before passing through for efficiency
+
+
+ - HTTP error responses:
+
- For many common and not-so-common errors, so the user knows what happened
+
- Over 20 unique translated, styled, and formatted error pages for various errors
+
- Internal web server to serve forms, CSS, images, and errors
+
+
+ - Transparent response decompression:
+
- If the server-side HTTP proxy compressed the response,
+the HTTP client proxy transparently decompresses it.
+
+
+
+
The i2ptunnel compression is requested with the HTTP header:
@@ -91,7 +134,7 @@ The response indicating i2ptunnel compression contains the following HTTP header
Depending on if the tunnel is using an outproxy or not it will append the following User-Agent:
{%- endtrans %}
-- {% trans %}Outproxy:{% endtrans %} User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.6) Gecko/20100625 Firefox/3.6.6
+- {% trans %}Outproxy:{% endtrans %} User-Agent: Uses the user agent from a recent Firefox release on Windows
- {% trans %}Internal I2P use:{% endtrans %} User-Agent: MYOB/6.66 (AN/ON)
@@ -101,8 +144,8 @@ Depending on if the tunnel is using an outproxy or not it will append the follow
Creates a connection to a random IRC server specified by the comma seprated (", ")
list of destinations. Only a whitelisted subset of IRC commands are allowed due to anonymity concerns.
{%- endtrans %}
-The following whitelist is for commands inbound from the IRC server to the IRC client.
-
{% trans %}Whitelist:{% endtrans %}
+The following allow list is for commands inbound from the IRC server to the IRC client.
+
Allow list:
- AUTHENTICATE
- CAP
@@ -173,7 +216,51 @@ Creates a destination to a local HTTP server ip:port. Supports gzip for requests
Accept-encoding: x-i2p-gzip, replies with Content-encoding: x-i2p-gzip in such a request.
{%- endtrans %}
+
+The HTTP server proxy provides a number of services to make hosting a website easier and more secure,
+and to provide a better user experience on the client side.
+
+
+- Request header processing:
+
- Header validation
+
- Header spoof protection
+
- Header size checks
+
- Optional inproxy and user-agent rejection
+
- Add X-I2P headers so the webserver knows where the request came from
+
- Host header replacement to make webserver vhosts easier
+
- Force connection: close
+
- RFC-compliant hop-by-hop header processing and stripping
+
- Buffering of all headers before passing through for efficiency
+
+
+ - DDoS protection:
+
- POST throttling
+
- Timeouts and slowloris protection
+
- Additional throttling happens in streaming for all tunnel types
+
+
+ - Response header processing:
+
- Stripping of some privacy-problematic headers
+
- Mime type and other headers check for whether to compress response
+
- Force connection: close
+
- RFC-compliant hop-by-hop header processing and stripping
+
- Buffering of all headers before passing through for efficiency
+
+
+ - HTTP error responses:
+
- For many common and not-so-common errors and on throttling, so the client-side user knows what happened
+
+
+ - Transparent response compression:
+
- The web server and/or the I2CP layer may compress, but the web server often does not,
+and it's most efficient to compress at a high layer, even if I2CP also compresses.
+The HTTP server proxy works cooperatively with the client-side proxy to transparently compress responses.
+
+
+
+
HTTP Bidirectional
+Deprecated
{% trans -%}
Functions as both a I2PTunnel HTTP Server, and a I2PTunnel HTTP client with no outproxying
capabilities. An example application would be a web application that does client-type