liveBook · Manning

Server-side validation

As explained in Acing the Frontend Interview

Server-side validation checks request data on the server before processing or storage.

Server validation checks submitted form data after the browser sends it and before the server processes it. The server checks the received data for integrity and authenticity. Client-side validation happens earlier, in the browser, and is a separate step. section 2.4

Trace a form submission

A user submits a form. The browser collects and encodes its fields, then sends an HTTP request. The server validates the received data before processing it, such as by storing it in a database. Its response lets the browser show either confirmation or errors the user can correct. section 2.4

In an interview, distinguish where each check runs: browser validation precedes the request; server validation follows receipt and precedes processing. Be ready to explain how a failed submission returns useful feedback. section 2.4

How Acing the Frontend Interview covers it

How deep it goes
Defines its place and purpose in the submission sequence but does not show server-side validation code.
Examples
Traces a form from browser validation through request encoding, server checks, processing, and success or error feedback.
What you can do after
Evaluate/understand where server checks belong in form submission and distinguish them from browser checks.
How it connects
Connects server validation to HTML forms, client-side validation, HTTP requests, database storage, and error feedback.

Also explained in

Compare how 5 books explain server-side validation →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Acing the Frontend Interview. The section links point to the parts of the book it draws on.