0 views collected around this technical thread.
This article explains the browser's same‑origin policy, its role in preventing XSS, CSRF and other attacks, details the protocol, host and port rules, illustrates with examples, and then describes CORS, simple and preflight requests, credential handling, and provides a complete request flow diagram.
This article explains the same‑origin policy, its role in protecting browsers from XSS, CSRF and other attacks, illustrates how origins are defined with protocol, host and port, and details how CORS, simple requests and preflight requests enable controlled cross‑origin communication.
This article explains the fundamentals of the same‑origin policy, the security risks it mitigates, and how CORS and preflight requests work in browsers, illustrating the concepts with diagrams, header details, and a complete request flow chart.
This article explains the browser's Same‑Origin Policy, its role in preventing XSS, CSRF and other attacks, and details how Cross‑Origin Resource Sharing (CORS) works, including simple requests, preflight requests, credential handling, and provides a complete request flow diagram.
This article explains how to diagnose and fix common CORS problems when a front‑end site on port 8080 accesses a back‑end service on port 59200 by configuring Nginx as a proxy, detailing the required response headers, handling preflight requests, and providing complete example configurations.
This article explains the CORS standard, how browsers enforce same‑origin policy, the definitions of simple and preflight requests, required HTTP headers, credential handling, and typical configuration mistakes that cause CORS errors, illustrated with code examples and tables.
This article walks through the root causes of CORS errors, explains the four essential response headers, demonstrates how to test with Postman, and provides a series of Nginx configuration examples that progressively fix preflight, header, method, and credential problems for a local development environment.
This article explains the mechanics of CORS, detailing how browsers decide whether a cross‑origin request is executed directly, blocked, or preceded by a preflight OPTIONS request, and distinguishes between simple and complex requests based on method, headers, and other criteria.
The article explains why CORS distinguishes between simple requests—limited to GET, HEAD, POST with specific headers and content types—and preflighted requests, describing the server‑side rationale, the mechanics of preflight, and why avoiding preflight for simple requests simplifies cross‑origin interactions.