-1
I would need to worry about the vulnerability of frontend or just with the backend?
2 answers
2
It’s not that you don’t have to worry, only you can never guarantee the security of your code because it can even be played aside and communicate with the backend without him, so anything you do there can be swindled if you want, so the greatest control should be on the server.
Which is not to say that you shouldn’t make proper code on the client to avoid an interception along the way, when both the server and the client want to work right and have something in the middle they don’t want, so it’s important to encrypt, maintain communication and authentication controls if applicable.
It is also important to make a code to give a better user experience, but not that it is because of security.
It may also be useful to maintain some protection to prevent a naive attack, but not for security purposes, don’t consider it an effective measure. Remember that everything that is on a computer that you have no control can not even trust what is running. And the computer you can trust, usually the server, is reliable until it’s hacked.
-1
I suggest you validate both the backend and the frontend. The validation made in frondend prevents error messages that the user does not understand from appearing to him and the validation made in the backend prevents smart users from scamming the system, using developer tools from the browser itself.
Browser other questions tagged node.js angular vue.js front-end security-guard
You are not signed in. Login or sign up in order to post.
Hi miner, yes, your reply was helpful to me, thank you!
– Rick Gostosao
Did any of the answers solve your question? Do you think you can accept one of them? Check out the [tour] how to do this, if you haven’t already. You would help the community by identifying what was the best solution for you. You can accept only one of them. But you can vote on any question or answer you find useful on the entire site (when you have enough score).
– Maniero