The hijacking you are talking about refers to the HTTP hijacking done by ISP? ISP's HTTP hijacking will only start after detecting the HTTP GET packet (hijack the packet and return 302, the process is probably like this) So don't say use https, cut the packet smaller, so that If the ISP cannot detect the complete HTTP GET request, the problem can be solved - But I don't know how to cut the data packet into smaller sizes. I think changing the MTU is useless, and the performance loss of changing the MTU is too great. It is recommended to go to https directly.
The hijacking you are talking about refers to the HTTP hijacking done by ISP?
ISP's HTTP hijacking will only start after detecting the HTTP GET packet (hijack the packet and return 302, the process is probably like this)
So don't say use https, cut the packet smaller, so that If the ISP cannot detect the complete HTTP GET request, the problem can be solved
- But I don't know how to cut the data packet into smaller sizes. I think changing the MTU is useless, and the performance loss of changing the MTU is too great.
It is recommended to go to https directly.
80% of the problem can be solved by using https