Can I paste a cURL command or fetch call from browser DevTools?+
Yes. Paste one Copy as cURL command or Copy as fetch call and press Apply to client. Parsing happens locally without eval or shell execution, nothing sends automatically, and the original pasted text is cleared after a successful import. Credential, cookie, proxy, forwarding, framing, and reserved browser headers are dropped with visible warnings; files and expressions are rejected. A valid Origin is retained for Server request mode.
Can this online HTTP client test an API without CORS?+
For a public default-port URL, select Server request and complete fresh Turnstile. The protected gateway makes one bounded request from odmin.biz infrastructure, so browser CORS does not hide the response. It is not a general proxy: private destinations, credentials, files, arbitrary ports, large requests, and automated replay remain unavailable.
Can a server request set Origin, Referer, or User-Agent?+
Yes. Protected Server request mode writes its own HTTP request and accepts bounded Referer and User-Agent values plus one syntactically valid HTTP(S) Origin. Direct browser mode remains subject to browser control, so Origin and Referer are server-only and a browser may normalize or withhold User-Agent.
Does the API tester support Authorization headers or cookies?+
No. Authorization, Cookie, URL credentials, and related credential-bearing options are deliberately blocked. If a copied cURL or fetch request contains them, the importer removes them and shows a warning rather than retaining or sending them.
What data leaves my browser?+
Import and cURL/fetch export are local and initiate no request. Direct GET/HEAD sends the URL and allowed headers to the destination from your browser. Server request sends the URL, method, allowed headers, text body, redirect choice, and one-time token to https://http-client.odmin.biz/. The application does not persist or intentionally log either flow.
How are redirects handled?+
Redirects are returned as-is by default. For GET or HEAD, follow redirects permits up to five HTTP or HTTPS 301, 302, 303, 307, or 308 locations. The gateway repeats all public-destination checks, verifies HTTPS identity, and strips custom headers when the origin changes.
What can I send?+
GET, HEAD, POST, PUT, PATCH, DELETE, and OPTIONS are supported. Up to 32 safe custom headers—including server-side Origin, Referer, and User-Agent—and a text body may be used, but the full request is capped at 16 KiB. Files, multipart uploads, cookies, authorization, URL credentials, forwarding fields, and transport-sensitive headers are blocked.
When is Turnstile required?+
It is required for every Server request and automatically for every method other than GET or HEAD. Direct browser GET/HEAD skips Turnstile because the request uses your own network context and remains subject to CORS.