network-request-auditing

To audit browser network requests, you navigate API-heavy pages in Cursor's built-in browser, perform interactions, and review the network log to detect 4xx/5xx responses, slow endpoints, and duplicate calls.

Yes, you can detect CORS errors and duplicate API calls by exercising user actions in Cursor's built-in browser. The network audit reviews the traffic log to flag security issues, duplicate calls, and preflight storms.

Browser network traffic auditing inspects network behavior after real user interactions to catch failed requests, duplicate calls, slow endpoints, and privacy issues. You need it when changing API-heavy pages like a checkout flow to verify saves and validations are healthy.

Yes, network-request-auditing works within Cursor's built-in browser. It applies after navigation and interactive testing, capturing a snapshot of network requests to report on method, URL pattern, status, timing, and security issues.

To check for sensitive data in URLs and missing auth, navigate your page in Cursor's browser and perform key actions. The network audit reviews the request log to flag suspicious payloads, unexpected third-party hosts, and missing authentication.

API calls might fail due to CORS problems, 4xx/5xx responses, or network errors. By auditing browser network traffic after interactive testing, you can review the method, URL pattern, and status of requests to identify the exact failure point.