744109cc78
Every session dialled a proxy on its own with nothing in between, so a cold start or a proxy switch opened one socket per session per account in the same millisecond. A public mtproxy answers about two parallel handshakes and silently drops the rest, which the client read back as client_hello_sent_no_server_hello or connected_no_mtproto_data across the whole batch - including on a dd-secret proxy that sends no ClientHello at all and therefore cannot be fingerprint-blocked. Replace the machinery that was supposed to prevent this with a rate limiter that actually does. ProxyDialLease keeps at most two unproven handshakes in flight per proxy server, spaces the rest apart and stretches the spacing after a run of attempts that proved nothing, so a blackholed proxy is no longer redialled by every session on its own eight second timer. Everything that reacted to failure by changing its own behaviour is gone: EndpointAdmissionArbiter, EndpointLivePool, ConnectionBroker, session_proxy_adapter, SessionProxyPort, HandshakeGate, open_scheduler, endpoint_health, adaptive_policy and ProxyRotationManager. A fingerprint filter is deterministic, so rotating emulated ClientHello profiles only hands the other side more of them, and escalated recipes (fragmentation, pacing) make the flow less browser-like rather than more - while the signal that drove the escalation could not tell a DPI box from a proxy refusing extra connections. The ClientHello templates themselves are untouched and the profile is now whatever the user configured, fixed. Also: ServerHello budget 2.5s -> 5s, mtproxy status reduces through the same ProxyConnectionStatus path as every other proxy type, and route memory is wired back up so an address that answered is dialled first and one that failed is dialled last. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
53 lines
1.6 KiB
C++
53 lines
1.6 KiB
C++
/*
|
|
This file is part of Telegram Desktop,
|
|
the official desktop application for the Telegram messaging service.
|
|
|
|
For license and copyright information please follow this link:
|
|
https://github.com/telegramdesktop/tdesktop/blob/master/LEGAL
|
|
*/
|
|
#pragma once
|
|
|
|
#include "base/basic_types.h"
|
|
#include "mtproto/runtime/connection_status_types.h"
|
|
|
|
#include <QtCore/QMutex>
|
|
|
|
#include <map>
|
|
#include <memory>
|
|
#include <set>
|
|
#include <vector>
|
|
|
|
namespace MTP {
|
|
|
|
// Diagnostics correlation shared by every account: a trace id ties all log
|
|
// lines of one connection attempt together, and runtime ids keep those
|
|
// attempts apart between accounts. This used to also carry per-endpoint
|
|
// health - verdicts, cooldowns, relay proofs - which is gone: the client no
|
|
// longer reacts to its own failure history.
|
|
class ProxyEndpointContext final {
|
|
public:
|
|
[[nodiscard]] ProxyRuntimeId registerRuntime();
|
|
void unregisterRuntime(ProxyRuntimeId runtimeId);
|
|
|
|
[[nodiscard]] ProxyTraceId nextTraceId(
|
|
ProxyConnectionAttempt attempt = {});
|
|
void updateTraceAttempt(const ProxyConnectionAttempt &attempt);
|
|
[[nodiscard]] bool traceActive(ProxyTraceId traceId) const;
|
|
[[nodiscard]] auto activeTracesForRuntime(
|
|
ProxyRuntimeId runtimeId) const
|
|
-> std::vector<ProxyConnectionAttempt>;
|
|
[[nodiscard]] bool finishTrace(ProxyTraceId traceId);
|
|
|
|
private:
|
|
mutable QMutex _mutex;
|
|
std::set<ProxyRuntimeId> _runtimes;
|
|
std::map<ProxyTraceId, ProxyConnectionAttempt> _activeTraces;
|
|
ProxyRuntimeId _lastRuntimeId = 0;
|
|
ProxyTraceId _lastTraceId = 0;
|
|
|
|
};
|
|
|
|
[[nodiscard]] auto CreateProxyEndpointContext()
|
|
-> std::shared_ptr<ProxyEndpointContext>;
|
|
|
|
} // namespace MTP
|