echelon/i2p.i2p
1
0
Fork 0
forked from I2P_Developers/i2p.i2p
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
Files
9ec2c62f2fe85d2ba97fc66fcc8af113e53b69a6
i2p.i2p/installer/resources/proxy/enc-header.ht

29 lines
1.4 KiB
Plaintext
Raw Normal View History

Proxy: Fix error code for incompatible encryption
2020-05-18 12:25:25 +00:00
HTTP/1.1 403 Incompatible Encryption Options
NetDB: - Better handling of unsupported encryption in destinations - Implement handling of unsupported encryption in router identities - Banlist forever all RIs with unsupported encryption - New negative cache of all dests with unsupported encryption - New methods for destination lookup that will succeed even if the LS is expired or encryption is unsupported - Use new dest lookup so client will get the right error code later, rather than failing with no LS when we really got it but just couldn't verify it. - Cleanups and javadocs OCMOSJ: Detect unsupported encryption on dest and return the correct failure code through I2CP to streaming to i2ptunnel Streaming: Re-enable message status override, but treat LS lookup failure as a soft failure for now. HTTP Client: Add error page for unsupported encryption
2014-09-05 22:52:23 +00:00
Content-Type: text/html; charset=UTF-8
i2ptunnel, eepget: Capitalize Cache-Control Change POST throttle response to 429
2018-02-14 12:54:16 +00:00
Cache-Control: no-cache
NetDB: - Better handling of unsupported encryption in destinations - Implement handling of unsupported encryption in router identities - Banlist forever all RIs with unsupported encryption - New negative cache of all dests with unsupported encryption - New methods for destination lookup that will succeed even if the LS is expired or encryption is unsupported - Use new dest lookup so client will get the right error code later, rather than failing with no LS when we really got it but just couldn't verify it. - Cleanups and javadocs OCMOSJ: Detect unsupported encryption on dest and return the correct failure code through I2CP to streaming to i2ptunnel Streaming: Re-enable message status override, but treat LS lookup failure as a soft failure for now. HTTP Client: Add error page for unsupported encryption
2014-09-05 22:52:23 +00:00
Connection: close
Proxy-Connection: close
i2ptunnel: Remove javascript from proxy error pages Add security headers Fix typo on resetp-header
2020-05-15 21:31:37 +00:00
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
Referrer-Policy: no-referrer
Content-Security-Policy: default-src 'none'; style-src 'self' 'unsafe-inline' http://proxy.i2p; form-action 'self' http://proxy.i2p; frame-ancestors 'self' http://127.0.0.1:7657/; img-src http://proxy.i2p
NetDB: - Better handling of unsupported encryption in destinations - Implement handling of unsupported encryption in router identities - Banlist forever all RIs with unsupported encryption - New negative cache of all dests with unsupported encryption - New methods for destination lookup that will succeed even if the LS is expired or encryption is unsupported - Use new dest lookup so client will get the right error code later, rather than failing with no LS when we really got it but just couldn't verify it. - Cleanups and javadocs OCMOSJ: Detect unsupported encryption on dest and return the correct failure code through I2CP to streaming to i2ptunnel Streaming: Re-enable message status override, but treat LS lookup failure as a soft failure for now. HTTP Client: Add error page for unsupported encryption
2014-09-05 22:52:23 +00:00
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html><head>
Proxy error page tweaks
2015-01-30 15:55:12 +00:00
<title>_("Website Unreachable")</title>
NetDB: - Better handling of unsupported encryption in destinations - Implement handling of unsupported encryption in router identities - Banlist forever all RIs with unsupported encryption - New negative cache of all dests with unsupported encryption - New methods for destination lookup that will succeed even if the LS is expired or encryption is unsupported - Use new dest lookup so client will get the right error code later, rather than failing with no LS when we really got it but just couldn't verify it. - Cleanups and javadocs OCMOSJ: Detect unsupported encryption on dest and return the correct failure code through I2CP to streaming to i2ptunnel Streaming: Re-enable message status override, but treat LS lookup failure as a soft failure for now. HTTP Client: Add error page for unsupported encryption
2014-09-05 22:52:23 +00:00
<link rel="shortcut icon" href="http://proxy.i2p/themes/console/images/favicon.ico">
<link href="http://proxy.i2p/themes/console/default/console.css" rel="stylesheet" type="text/css">
</head>
<body>
<div class="logo">
<a href="http://127.0.0.1:7657/" title="_("Router Console")"><img src="http://proxy.i2p/themes/console/images/i2plogo.png" alt="_("I2P Router Console")" border="0"></a><hr>
Proxy: Clean up links in error pages
2019-12-18 12:23:49 +00:00
<a href="http://127.0.0.1:7657/config">_("Configuration")</a> <a href="http://127.0.0.1:7657/help">_("Help")</a> <a href="http://127.0.0.1:7657/dns">_("Addressbook")</a>
NetDB: - Better handling of unsupported encryption in destinations - Implement handling of unsupported encryption in router identities - Banlist forever all RIs with unsupported encryption - New negative cache of all dests with unsupported encryption - New methods for destination lookup that will succeed even if the LS is expired or encryption is unsupported - Use new dest lookup so client will get the right error code later, rather than failing with no LS when we really got it but just couldn't verify it. - Cleanups and javadocs OCMOSJ: Detect unsupported encryption on dest and return the correct failure code through I2CP to streaming to i2ptunnel Streaming: Re-enable message status override, but treat LS lookup failure as a soft failure for now. HTTP Client: Add error page for unsupported encryption
2014-09-05 22:52:23 +00:00
</div>
<div class="warning" id="warning">
Proxy error page tweaks
2015-01-30 15:55:12 +00:00
<h3>_("Website Unreachable")</h3>
NetDB: - Better handling of unsupported encryption in destinations - Implement handling of unsupported encryption in router identities - Banlist forever all RIs with unsupported encryption - New negative cache of all dests with unsupported encryption - New methods for destination lookup that will succeed even if the LS is expired or encryption is unsupported - Use new dest lookup so client will get the right error code later, rather than failing with no LS when we really got it but just couldn't verify it. - Cleanups and javadocs OCMOSJ: Detect unsupported encryption on dest and return the correct failure code through I2CP to streaming to i2ptunnel Streaming: Re-enable message status override, but treat LS lookup failure as a soft failure for now. HTTP Client: Add error page for unsupported encryption
2014-09-05 22:52:23 +00:00
<p>
more renaming
2015-01-08 18:20:08 +00:00
_("The website was not reachable, because it uses encryption options that are not supported by your I2P or Java version.")
NetDB: - Better handling of unsupported encryption in destinations - Implement handling of unsupported encryption in router identities - Banlist forever all RIs with unsupported encryption - New negative cache of all dests with unsupported encryption - New methods for destination lookup that will succeed even if the LS is expired or encryption is unsupported - Use new dest lookup so client will get the right error code later, rather than failing with no LS when we really got it but just couldn't verify it. - Cleanups and javadocs OCMOSJ: Detect unsupported encryption on dest and return the correct failure code through I2CP to streaming to i2ptunnel Streaming: Re-enable message status override, but treat LS lookup failure as a soft failure for now. HTTP Client: Add error page for unsupported encryption
2014-09-05 22:52:23 +00:00
<hr>
<p><b>_("Could not connect to the following destination:")</b>
</p>
Reference in New Issue Copy Permalink