亚洲国产日韩欧美一区二区三区,精品亚洲国产成人av在线,国产99视频精品免视看7,99国产精品久久久久久久成人热,欧美日韩亚洲国产综合乱

Pure back-end rendering, no ajax required

How can the security of the backend be guaranteed by the frontend?

You can only sign a parameter at most

You can try using a relay server. Assuming that server B needs to be kept secret, you can instead request server A, and then use server A to forward the request to server B, so that B’s address will not be exposed

You can only be relatively hidden but not completely hidden

Isn’t it enough to just make a custom browser? If you customize a network protocol, you won’t be able to see it. If you want to use a network protocol, you still want people to not be able to see it? The app can capture packets for you.

Don’t release the project, it’s absolutely confidential

In terms of simple hidden interfaces: secondary encapsulation
You write a method on the server to request the interface. You point ajax to the secondary encapsulation method, so that the page sees that the request is your secondary encapsulation. Method, and then do some anti-counterfeiting requirements and security processing.

clearconsole();

What should I do if the console is not displayed and the network is displayed? Even if it is not displayed, what should I do if someone else captures the packets? The boy gave up his resistance. The front end is clear and not confidential. Let them fiddle with the back end

1. Back-end rendering, all data uses templates.
2.Transfer service

And I feel that there is no need to block. The front end is not safe anyway. To avoid packet capture, https can be used to improve security.