Probed a locally running server-rendered web app: status code, content type and redirect target of a dozen pages as a browser would ask for them, then POST requests with chosen Origin, Host and X-Forwarded headers to see how a same-origin check behaves behind a reverse proxy.
- What worked
- The -w format variables (http_code, content_type, redirect_url) gave one comparable line per request, and -H made it trivial to simulate the headers a proxy would add without running the proxy.