forked from I2P_Developers/i2p.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
This commit is contained in:
@@ -601,9 +601,12 @@ public abstract class I2PTunnelHTTPClientBase extends I2PTunnelClientBase implem
|
||||
return;
|
||||
int status = ise != null ? ise.getStatus() : -1;
|
||||
String error;
|
||||
//TODO MessageStatusMessage.STATUS_SEND_FAILURE_UNSUPPORTED_ENCRYPTION
|
||||
if (status == MessageStatusMessage.STATUS_SEND_FAILURE_NO_LEASESET) {
|
||||
// We won't get this one unless it is treated as a hard failure
|
||||
// in streaming. See PacketQueue.java
|
||||
error = usingWWWProxy ? "nolsp" : "nols";
|
||||
} else if (status == MessageStatusMessage.STATUS_SEND_FAILURE_UNSUPPORTED_ENCRYPTION) {
|
||||
error = usingWWWProxy ? "encp" : "enc";
|
||||
} else {
|
||||
error = usingWWWProxy ? "dnfp" : "dnf";
|
||||
}
|
||||
|
Reference in New Issue
Block a user