3 ms·
I meant a little more abstract description of what the page is trying to do. I presume you are processing some client-side information and sending the output i
by dlcarrier 2y ago
I meant a little more abstract description of what the page is trying to do.
I presume you are processing some client-side information and sending the output in a GET request, and you want to prevent the user from sending a nefarious GET request with inauthentic data?
In general, you will need to sanitize the inputs on the server side, to ensure only sensible GET requests are acknowledged, but there will likely need to be more done to verify that the data itself is authentic.
Can you give me an overview of how the information in a valid GET request is obtained, and what a user might be attempting to accomplish with nefarious GET request?
I don't mean source code, just some goals of what you are trying to accomplish by hosting the page, what goals a normal user would be accomplishing in using the page, and the goals a bad actor may have that you are trying to prevent.
- 01-_- 2y agosend votes with user names that are not in the database, for example. That's what a bad person could do. But for those who are logged in, they can do so with proof of the data already registered in the database.