Skip to content

How a PHP Request Works, from Browser to SQLite

When you click Add book in the PHP and SQLite reading list, your browser makes two HTTP requests. The first saves the title. The second gets the updated page.

Browser -- POST / --> Development web server
|
v
PHP (index.php)
| PDO INSERT
v
SQLite file
|
PHP sends 303
|
Browser <-- Location: / --- Server
Browser -- GET / ---> Development web server
|
PHP runs SELECT
|
Browser <-- 200 HTML -------+
  1. The browser sends POST / with the title, form action, and session token.
  2. The web server receives the request and invokes public/index.php. The local PHP development server handles both roles in one process.
  3. The PHP runtime checks the submitted token against the session and validates the title. PDO runs an INSERT with the title as a bound parameter. SQLite stores the book in a file on disk.
  4. After saving, PHP sends 303 See Other with Location: /. The server passes that response to the browser.
  5. The browser follows with GET /. PHP runs a SELECT, escapes the saved titles, and returns 200 OK with HTML. Refreshing the page repeats the GET.
  1. Run the app from the starter instructions and open the reading list at http://127.0.0.1:8000/.
  2. Open your browser’s developer tools and select Network. Enable Preserve log, clear the request list, and add a book with a title such as The PHP Field Guide.
  3. Select the request with method POST and status 303. In its headers, find Location: /.
  4. Select the following GET with status 200. The response contains the rendered list and your new title.
  5. Refresh. Check for another GET and confirm your title appears once.

Try to predict which HTTP request you would inspect if the book never reached the database, or if it was saved but the page displayed it incorrectly. The PDO lesson explains the database calls. The HTTP router lesson shows how a multi-page app chooses different PHP handlers for different requests.