liveBook · Manning

Browser

As explained in Spring Security in Action, Second Edition

A web browser is client software that retrieves, renders, and executes web resources on behalf of a user.

A browser retrieves a page, runs its JavaScript, sends web requests, and decides whether to expose responses to the page. For cross-origin calls, it checks server-provided CORS headers; a request may reach the server while its response remains inaccessible to the page. section 10.1

A browser’s CORS behavior becomes visible when an application uses different origin strings:

  • Treats localhost:8080 and 127.0.0.1:8080 as different domains, even when they refer to the same host. section 10.1

How Spring Security in Action, Second Edition covers it

How deep it goes
Explains request, response, and preflight behavior through a Spring example, stopping short of browser internals.
Examples
Uses localhost versus 127.0.0.1, XMLHttpRequest POST requests, CORS errors, and server logs.
What it assumes
Assumes a page can run JavaScript and make XMLHttpRequest calls to an HTTP endpoint.
What you can do after
Diagnose cross-origin failures by comparing origins, response headers, preflight behavior, and server execution logs.
How it connects
Connects browser behavior with CORS, HTTP requests, JavaScript, and Spring Security.

Also explained in

Compare how 3 books explain browser →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Spring Security in Action, Second Edition. The section links point to the parts of the book it draws on.