database64128

What about combining unsafe stream prefix with unsafe fallback? And use the fallback domain as part of the prefix. For example, if the fallback address is `example.com:80`, change the `Host`...

Thank you for bearing with me and keeping the experiment going! 😄 At this point it's still not clear what characteristics are triggering the blocking. gfw-report/shadowsocks-rust@d1cf917deebe1999044ca93965a602223de26be7 adjusts the 1/0 ratio...

This does not seem like how the GFW blocks things. Can you also check the corresponding server log message?

I found a Vultr server in the same situation as yours, and experimented with it. A few things I've found out about so far: 1. This type of blocking only...

> If I replace client/server with shadowsocks-rust (with same 2022 ciphers) Did you mean replacing both client and server, or either of them? Which combinations work and which ones don't?...

> fixed the issue Good. WoW's server is likely the one at fault here. The person who wrote the offending code was probably not familiar with TCP semantics. And they...

No, it's unrelated. The option for initial payload buffer size will be added at a later time.

Done in cb5061f05b572b5be7eb7cca91a9a299405d979b.

Hmm, that's interesting. There are still a few things you could try before the only option we have left is packet capture. 1. On the client side, lower `initialPayloadWaitTimeout`. The...

There's the REST API for server management. It's currently not documented in README, as [the spec](https://github.com/Shadowsocks-NET/shadowsocks-specs/pull/3) is not finalized yet. But you could find its config fields in the [full...