Security issues when JS accesses Webservice_html/css_WEB-ITnose

1. Direct access to Webservice via js is not very safe. How to improve security? ? ? Because all actions performed by JS can be seen in the browser.

Is there any parameter encryption or other data access encryption methods? ? ?

2. Is it safer to directly output HTML in the background? ? ? Then Ajax requests the HTML output in the background and then loads it into the page?

3. Are there any other methods?

Reply to discussion (solution)

Has anyone answered? ? ?

The security of js accessing Webservice is the same as accessing html page

The security issue is done by providing the Webservice server.
What is done by the client is normal. Next, verify the legality of the data

Because as you know, no matter what, I can bypass a series of verifications on the client and submit the data to the Webservice.

The webservice can be seen when accessing the front end, but our js cannot be compiled no matter what.​ ​ ​
At most, you can only agree on an access agreement with the backend to encrypt and decrypt the access data.

What js does is page data access, legality judgment, page jump, page special effects and switching, etc.