[Blog](https://scrapfly.io/blog) / [http](https://scrapfly.io/blog/tag/http) / [How to Set Axios Headers: Complete Guide with Examples (2026)](https://scrapfly.io/blog/posts/guide-to-javascript-axios-headers) # How to Set Axios Headers: Complete Guide with Examples (2026) by [Ziad Shamndy](https://scrapfly.io/blog/author/ziad) Apr 18, 2026 16 min read [\#http](https://scrapfly.io/blog/tag/http) [\#javascript](https://scrapfly.io/blog/tag/javascript) [\#nodejs](https://scrapfly.io/blog/tag/nodejs) [ ](https://www.linkedin.com/sharing/share-offsite/?url=https%3A%2F%2Fscrapfly.io%2Fblog%2Fposts%2Fguide-to-javascript-axios-headers "Share on LinkedIn") [Axios](https://www.npmjs.com/package/axios/) is the most popular HTTP client in JavaScript. Headers control how every request and response behaves. Whether you're attaching auth tokens, setting content types, or rotating User-Agents for web scraping, getting headers right prevents 401s and 403s. This guide covers every Axios header pattern you'll need. Per-request config, global defaults, instances, interceptors, header merging, response inspection, pitfalls, and scraping headers. Each section stands alone, so jump to what you need. ## Key Takeaways Here are the key Axios header patterns covered in this guide: - Pass headers in the config object: second argument for GET/DELETE, third argument for POST/PUT (after the data parameter) - Set global defaults with `axios.defaults.headers.common` for headers that apply to every request, or use `axios.create()` for isolated instances - Use request interceptors to inject auth tokens before every request, and response interceptors to refresh expired tokens on 401 - Axios merges headers in order: library defaults, global defaults, instance defaults, per-request config, then interceptors (last write wins) - Access `response.headers` to read rate limits, caching signals, and API metadata (Axios lowercases all header names) - For web scraping, set browser-like User-Agent and Accept headers via interceptors that rotate values across requests **Get web scraping tips in your inbox**Trusted by 100K+ developers and 30K+ enterprises. Unsubscribe anytime. ## How Do You Add Headers to Axios Requests? Pass a `headers` object in the request config. For GET and DELETE, headers go in the second argument. For POST, PUT, and PATCH, headers go in the third argument (after the data parameter). ### How Do You Set Headers for a GET Request? javascript```javascript import axios from "axios"; // GET: headers are in the 2nd argument (the config object) const response = await axios.get("https://httpbin.dev/headers", { headers: { Authorization: "Bearer my-secret-token", Accept: "application/json", }, }); console.log(response.data); ``` The config object is the second parameter for `axios.get()`. Every header you set here applies only to this request. Other requests made through the same Axios instance stay unaffected. The `Authorization` header sends a Bearer token for API authentication. The `Accept` header tells the server you want JSON back. Both are standard patterns for REST API calls. ### How Do You Set Headers for a POST Request? javascript```javascript import axios from "axios"; // POST: data is the 2nd arg, headers go in the 3rd arg (config object) const response = await axios.post( "https://httpbin.dev/post", { username: "demo", action: "login" }, // request body (2nd arg) { headers: { Authorization: "Bearer my-secret-token", "Content-Type": "application/json", }, } // config with headers (3rd arg) ); console.log(response.data); ``` The most common Axios mistake is putting headers inside the data object instead of the config object. Headers always go in the third argument for POST, after the request body. The GET/POST signature mismatch catches many developers off guard. GET takes two arguments (URL and config), while POST takes three (URL, data, and config). If your POST request sends the auth token as part of the request body instead of as a header, the API will reject the call with a 401. Always double-check which argument slot your headers are in. ### How Do You Set Headers for PUT and DELETE Requests? javascript```javascript import axios from "axios"; // PUT follows the POST pattern: data (2nd), config (3rd) await axios.put( "https://httpbin.dev/put", { name: "updated-value" }, { headers: { Authorization: "Bearer my-secret-token" } } ); // DELETE has no body, so headers go in the 2nd arg (like GET) await axios.delete("https://httpbin.dev/delete", { headers: { Authorization: "Bearer my-secret-token" }, }); ``` PUT follows the same pattern as POST: data second, config third. DELETE takes no body, so headers go in the second argument like GET. If a request fails due to network or server errors, you can add retry logic to handle transient failures. See our [guide to retrying Axios requests](https://scrapfly.io/blog/posts/how-to-retry-in-axios) for patterns that work well with custom headers. [How Headers Are Used to Block Web Scrapers and How to Fix ItIntroduction to web scraping headers - what do they mean, how to configure them in web scrapers and how to avoid being blocked.](https://scrapfly.io/blog/posts/how-to-avoid-web-scraping-blocking-headers) With per-request headers covered, the next step is removing repetition by setting defaults. ## How Do You Set Default Headers for All Axios Requests? Use `axios.defaults.headers.common` for headers that apply to every request, or create isolated instances with `axios.create()` when different APIs need different headers. ### How Do You Set Global Headers with axios.defaults? javascript```javascript import axios from "axios"; // Common: applies to ALL request methods axios.defaults.headers.common["Authorization"] = "Bearer my-global-token"; // Method-specific: only applies to POST requests axios.defaults.headers.post["Content-Type"] = "application/json"; // Method-specific: only applies to GET requests axios.defaults.headers.get["Accept"] = "application/json"; // Now every request includes the Authorization header const response = await axios.get("https://httpbin.dev/headers"); console.log(response.data); ``` The `.common` key sets headers for all HTTP methods. Method-specific keys like `.get` and `.post` only apply to those methods. Be careful with global auth headers if you send requests to multiple origins. A global `Authorization` header leaks your token to every domain you call. If your app talks to both your own API and a third-party service, use instances instead of global defaults. ### How Do You Create Axios Instances with Custom Headers? javascript```javascript import axios from "axios"; // Instance for your internal API const internalApi = axios.create({ baseURL: "https://internal-api.example.com", headers: { Authorization: "Bearer internal-token", "X-Service": "frontend", }, }); // Instance for an external third-party API const externalApi = axios.create({ baseURL: "https://httpbin.dev", headers: { "X-API-Key": "external-key-123", }, }); // Each instance uses its own headers, no leakage const internalData = await internalApi.get("/users"); const externalData = await externalApi.get("/headers"); // You can also modify instance headers after creation externalApi.defaults.headers.common["Accept-Language"] = "en-US"; ``` Instances isolate header configs so your internal auth token never leaks to external services. Each instance maintains its own defaults, interceptors, and base URL. Changes to one instance don't affect the other. You can also modify instance headers after creation with `instance.defaults.headers.common[...]`. Updating headers after creation is useful when you receive a token after a login flow. Static defaults cover many cases, but some headers need to change at runtime. Interceptors handle that. ## How Do You Use Interceptors to Manage Headers Dynamically? Axios interceptors let you hook into every request or response to inject, update, or remove headers on the fly. The most common use is attaching auth tokens automatically. ### How Do You Inject Authorization Headers Automatically? javascript```javascript import axios from "axios"; // Browser: read token from localStorage axios.interceptors.request.use((config) => { const token = localStorage.getItem("auth_token"); if (token) { config.headers.Authorization = `Bearer ${token}`; } return config; }); // Node.js: read token from a module-level variable let currentToken = "initial-token"; axios.interceptors.request.use((config) => { if (currentToken) { config.headers.Authorization = `Bearer ${currentToken}`; } return config; }); // Every request now includes the latest token const response = await axios.get("https://httpbin.dev/headers"); console.log(response.data); ``` The request interceptor runs before every request, so it always picks up the latest token. You don't need to pass headers manually on each call. This pattern works for any header that changes at runtime: API keys that rotate, session IDs, CSRF tokens, or request timestamps. In browsers, `localStorage` is the typical token store. In Node.js, use a module-level variable or an environment variable. The interceptor pattern stays the same either way. ### How Do You Refresh Expired Tokens with Response Interceptors? javascript```javascript import axios from "axios"; // Separate instance for auth calls (prevents interceptor recursion) const authClient = axios.create({ baseURL: "https://auth.example.com" }); axios.interceptors.response.use( (response) => response, // Pass through successful responses async (error) => { const originalRequest = error.config; // Only retry once (prevent infinite loops) if (error.response?.status === 401 && !originalRequest._retry) { originalRequest._retry = true; try { // Refresh the token using the separate auth client const refreshResponse = await authClient.post("/refresh", { refresh_token: localStorage.getItem("refresh_token"), }); const newToken = refreshResponse.data.access_token; localStorage.setItem("auth_token", newToken); // Update the failed request's header and retry originalRequest.headers.Authorization = `Bearer ${newToken}`; return axios(originalRequest); } catch (refreshError) { // Refresh failed: clear tokens and redirect to login localStorage.removeItem("auth_token"); localStorage.removeItem("refresh_token"); window.location.href = "/login"; return Promise.reject(refreshError); } } return Promise.reject(error); } ); ``` The `_retry` flag prevents infinite retry loops when the refresh itself fails. Using a separate `authClient` instance avoids triggering the interceptor recursively during the refresh call. Without the separate instance, the refresh request would hit the same 401 interceptor, creating an infinite loop. This pattern handles the full token lifecycle: the request interceptor injects tokens, and the response interceptor refreshes expired tokens. You can extend the same approach for role-based headers or conditional auth schemes. With defaults, instances, and interceptors all setting headers, the question becomes: which value wins? ## How Does Axios Merge Headers from Multiple Sources? When you set headers at multiple levels, Axios merges them in a fixed order. Library defaults get overridden by global defaults, then instance defaults, then per-request config. Request interceptors run after the merge and get the final say. javascript```javascript import axios from "axios"; // Level 1: Global default axios.defaults.headers.common["X-Source"] = "global"; // Level 2: Instance default const api = axios.create({ baseURL: "https://httpbin.dev", headers: { "X-Source": "instance" }, }); // Level 3: Interceptor (runs last, overrides everything) api.interceptors.request.use((config) => { config.headers["X-Source"] = "interceptor"; return config; }); // Level 4: Per-request config const response = await api.get("/headers", { headers: { "X-Source": "per-request" }, }); // Result: X-Source = "interceptor" (interceptor runs last) console.log(response.data); ``` The interceptor wins because it runs after all other merging. To let per-request headers take priority over interceptors, add a guard: javascript```javascript api.interceptors.request.use((config) => { // Only set X-Source if the request didn't already specify one if (!config.headers["X-Source"]) { config.headers["X-Source"] = "interceptor-default"; } return config; }); ``` The full precedence chain: **library defaults → global defaults → instance defaults → per-request config → interceptors**. Knowing this order prevents headers from silently overriding each other. ## How Do You Read and Inspect Response Headers in Axios? Every Axios response includes a `response.headers` object with all server-sent headers. Use response headers to track rate limits, content types, pagination tokens, and caching metadata. javascript```javascript import axios from "axios"; const response = await axios.get("https://httpbin.dev/headers"); // Header names are normalized to lowercase in Axios console.log("Content-Type:", response.headers["content-type"]); console.log("Rate Limit Remaining:", response.headers["x-ratelimit-remaining"]); console.log("ETag:", response.headers["etag"]); ``` Axios normalizes all header names to lowercase, so always use lowercase when reading them (`"content-type"`, not `"Content-Type"`). For more on header casing rules, check our [guide to HTTP header casing](https://scrapfly.io/blog/answers/what-case-should-http-headers-be). You can use ETag headers for conditional requests that save bandwidth: javascript```javascript import axios from "axios"; // First request: store the ETag const first = await axios.get("https://httpbin.dev/etag/test-etag"); const etag = first.headers["etag"]; // Second request: send If-None-Match to check if content changed try { const second = await axios.get("https://httpbin.dev/etag/test-etag", { headers: { "If-None-Match": etag }, }); console.log("Content changed:", second.data); } catch (error) { if (error.response?.status === 304) { console.log("Content unchanged, use cached version"); } } ``` The conditional request returns 304 (Not Modified) when the content hasn't changed, saving bandwidth and server load. ETags work well for polling APIs where data changes infrequently. Common response headers worth inspecting: - `x-ratelimit-remaining`: how many API calls you have left before throttling - `x-ratelimit-reset`: when your rate limit resets (usually a Unix timestamp) - `content-type`: confirms the response format (JSON, HTML, XML) - `etag` / `last-modified`: caching tokens for conditional requests - `link`: pagination URLs in APIs that use link headers ## How Do You Handle Common Axios Header Problems? Most Axios header issues trace back to four causes: manual Content-Type on uploads, CORS blocks in browsers, missing cookie credentials, and header casing. ### Why Does File Upload Fail with Manual Content-Type? Setting `Content-Type: multipart/form-data` manually strips the boundary parameter that the server needs to parse the upload. Let Axios (or FormData) set the Content-Type automatically. javascript```javascript import axios from "axios"; import FormData from "form-data"; const form = new FormData(); form.append("file", fileBuffer, "document.pdf"); // BAD: manually setting Content-Type loses the boundary // axios.post(url, form, { headers: { "Content-Type": "multipart/form-data" } }) // GOOD: let FormData handle the Content-Type (includes boundary) await axios.post("https://httpbin.dev/post", form, { headers: form.getHeaders(), // Node.js: includes correct Content-Type + boundary }); // ALSO GOOD: in browsers, just pass the FormData (Axios detects it) // await axios.post("https://httpbin.dev/post", form); ``` In Node.js, call `form.getHeaders()` to get the right Content-Type with boundary. In browsers, pass the FormData object directly and Axios handles the header. ### How Do You Handle CORS Headers in Axios? CORS (Cross-Origin Resource Sharing) blocks happen in browsers, not in Node.js. When you send a request from `localhost:3000` to `api.example.com`, the browser checks whether the server allows cross-origin access. If the server doesn't send the right `Access-Control-Allow-*` headers, the browser blocks the response. Axios can't bypass this client-side. The difference between browser and Node.js is important: - **Browser**: CORS enforced by the browser. Custom headers blocked unless the server whitelists them. You can't skip CORS from client-side code - **Node.js**: No CORS enforcement at all. Full control over every header - **Workaround**: If you control the server, add `Access-Control-Allow-Origin` and `Access-Control-Allow-Headers` to the response. If you don't, proxy the request through your own backend javascript```javascript import axios from "axios"; import https from "https"; // Node.js: no CORS restrictions, full header control // You can even skip certificate validation for self-signed certs const agent = new https.Agent({ rejectUnauthorized: false }); const response = await axios.get("https://self-signed.example.com/api", { httpsAgent: agent, }); ``` In browsers, CORS errors mean the server needs to add `Access-Control-Allow-Origin` and `Access-Control-Allow-Headers` to its response. Axios can't fix a server-side CORS config. For more on dealing with blocked requests, see our [guide to 403 Forbidden errors](https://scrapfly.io/blog/posts/403-forbidden-web-scraping). ### Why Are Cookies Not Sent with Axios Requests? By default, Axios doesn't send cookies on cross-origin requests. Set `withCredentials: true` to include them: javascript```javascript import axios from "axios"; // Per-request await axios.get("https://api.example.com/me", { withCredentials: true }); // Or globally axios.defaults.withCredentials = true; ``` For cookies to work cross-origin, three conditions must be true: - Your Axios config sets `withCredentials: true` - The server responds with `Access-Control-Allow-Credentials: true` - The server's `Access-Control-Allow-Origin` is a specific origin (not `*`) Cookie `SameSite` and `Secure` attributes also affect delivery. Browsers won't send a `SameSite=Strict` cookie on any cross-origin request, even with `withCredentials: true`. ### Are Axios Header Names Case-Sensitive? Axios normalizes header names to lowercase internally. But some legacy backends reject lowercase headers. Stick with standard casing (`X-API-Key` rather than `x-api-key`) to avoid problems with picky servers. ## How Do You Set Headers for Web Scraping with Axios? Web scraping with Axios needs browser-like headers to avoid detection. At minimum, set a realistic User-Agent, Accept, and Accept-Language header. Interceptors make rotating these across requests easy. Servers inspect request headers to tell bots from real browsers. A missing or generic User-Agent is the fastest way to get blocked. For a closer look at User-Agent strategies, see our [User-Agent header guide](https://scrapfly.io/blog/posts/user-agent-header-in-web-scraping). javascript```javascript import axios from "axios"; // Create a scraping-focused instance with browser-like headers const scraper = axios.create({ headers: { "User-Agent": "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/125.0.0.0 Safari/537.36", Accept: "text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8", "Accept-Language": "en-US,en;q=0.5", "Accept-Encoding": "gzip, deflate, br", }, timeout: 15000, }); const response = await scraper.get("https://httpbin.dev/headers"); console.log(response.data); ``` This instance sends headers that match a real Chrome browser. For longer scraping sessions, rotate the User-Agent with an interceptor: javascript```javascript const userAgents = [ "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/125.0.0.0 Safari/537.36", "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/124.0.0.0 Safari/537.36", "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/125.0.0.0 Safari/537.36", ]; // Rotate User-Agent on every request scraper.interceptors.request.use((config) => { const randomAgent = userAgents[Math.floor(Math.random() * userAgents.length)]; config.headers["User-Agent"] = randomAgent; return config; }); ``` The interceptor picks a random User-Agent before each request, which reduces fingerprint-based detection. Scrapfly #### Scale your web scraping effortlessly Scrapfly handles proxies, browsers, and anti-bot bypass — so you can focus on data. [Try Free →](https://scrapfly.io/register)## Powerup with ScrapFly ScrapFly provides web scraping, screenshot, and extraction APIs for data collection at scale. For teams scaling past manual header management, Scrapfly handles the complexity automatically. Key features for Axios-based scraping projects: - [Anti-Scraping Protection (ASP)](https://scrapfly.io/docs/scrape-api/anti-scraping-protection) bypasses bot detection without manual header tuning - Rotating residential proxies across 100+ countries - Built-in JavaScript rendering through headless browsers - [TypeScript SDK](https://scrapfly.io/docs/sdk/typescript) for direct integration with Node.js projects Self-managed Axios setups with proxy rotation work well for smaller projects. For the full Node.js scraping setup, see our [web scraping with Node.js guide](https://scrapfly.io/blog/posts/web-scraping-with-nodejs). Also check our [Axios proxy configuration guide](https://scrapfly.io/blog/answers/how-to-use-proxies-nodejs-axios). ### Web Scraping API Scrape any website with our powerful API. Anti-bot bypass, JavaScript rendering, and rotating proxies built-in. [Try Web Scraping API](https://scrapfly.io/docs/scrape-api/getting-started) ## FAQ Does Axios automatically set the Content-Type header?Yes. Axios sets `Content-Type: application/json` when you pass a JavaScript object as the body, and `application/x-www-form-urlencoded` for URLSearchParams. Don't override Content-Type manually for FormData uploads (see the troubleshooting section above). Can you override global Axios headers for a single request?Yes. Any header in the per-request config takes priority over global and instance defaults. Per-request overrides let you keep global settings for most calls while customising one request. How do you remove a default header for one request?Set the header value to `undefined` in the per-request config: `headers: { Authorization: undefined }`. Axios skips headers with `undefined` values for that specific request. Does Axios support setting multiple headers with the same name?No. Axios doesn't support duplicate header names. The last value set for a header overwrites previous values. Use comma-separated values in a single header when the HTTP spec allows it. How do you send cookies with Axios cross-origin requests?Set `withCredentials: true` in your Axios config. The server must also respond with `Access-Control-Allow-Credentials: true` and a specific (non-wildcard) `Access-Control-Allow-Origin` header. How do you set headers in Axios with TypeScript?Use the `AxiosRequestConfig` type: `const config: AxiosRequestConfig = { headers: { Authorization: 'Bearer token' } }`. Axios v1+ ships with built-in TypeScript types. No extra `@types` package required. ## Summary Axios gives you five layers of header management: per-request config, global defaults, instances, interceptors, and response inspection. The merging order (library, global, instance, request, interceptor) decides which value wins when they overlap. Knowing this order prevents silent header conflicts. For web scraping at scale, header management (User-Agent rotation, anti-detection headers, proxy auth) gets complex fast. [Scrapfly](https://scrapfly.io) handles that complexity automatically for teams that need it. For smaller projects, self-managed Axios setups with the patterns in this guide work well. Legal Disclaimer and PrecautionsThis tutorial covers popular web scraping techniques for education. Interacting with public servers requires diligence and respect: - Do not scrape at rates that could damage the website. - Do not scrape data that's not available publicly. - Do not store PII of EU citizens protected by GDPR. - Do not repurpose *entire* public datasets which can be illegal in some countries. Scrapfly does not offer legal advice but these are good general rules to follow. For more you should consult a lawyer. Table of Contents- [Key Takeaways](#key-takeaways) - [How Do You Add Headers to Axios Requests?](#how-do-you-add-headers-to-axios-requests) - [How Do You Set Headers for a GET Request?](#how-do-you-set-headers-for-a-get-request) - [How Do You Set Headers for a POST Request?](#how-do-you-set-headers-for-a-post-request) - [How Do You Set Headers for PUT and DELETE Requests?](#how-do-you-set-headers-for-put-and-delete-requests) - [How Do You Set Default Headers for All Axios Requests?](#how-do-you-set-default-headers-for-all-axios-requests) - [How Do You Set Global Headers with axios.defaults?](#how-do-you-set-global-headers-with-axios-defaults) - [How Do You Create Axios Instances with Custom Headers?](#how-do-you-create-axios-instances-with-custom-headers) - [How Do You Use Interceptors to Manage Headers Dynamically?](#how-do-you-use-interceptors-to-manage-headers-dynamically) - [How Do You Inject Authorization Headers Automatically?](#how-do-you-inject-authorization-headers-automatically) - [How Do You Refresh Expired Tokens with Response Interceptors?](#how-do-you-refresh-expired-tokens-with-response-interceptors) - [How Does Axios Merge Headers from Multiple Sources?](#how-does-axios-merge-headers-from-multiple-sources) - [How Do You Read and Inspect Response Headers in Axios?](#how-do-you-read-and-inspect-response-headers-in-axios) - [How Do You Handle Common Axios Header Problems?](#how-do-you-handle-common-axios-header-problems) - [Why Does File Upload Fail with Manual Content-Type?](#why-does-file-upload-fail-with-manual-content-type) - [How Do You Handle CORS Headers in Axios?](#how-do-you-handle-cors-headers-in-axios) - [Why Are Cookies Not Sent with Axios Requests?](#why-are-cookies-not-sent-with-axios-requests) - [Are Axios Header Names Case-Sensitive?](#are-axios-header-names-case-sensitive) - [How Do You Set Headers for Web Scraping with Axios?](#how-do-you-set-headers-for-web-scraping-with-axios) - [Powerup with ScrapFly](#powerup-with-scrapfly) - [FAQ](#faq) - [Summary](#summary) Join the Newsletter Get monthly web scraping insights Scale Your Web Scraping Anti-bot bypass, browser rendering, and rotating proxies, all in one API. Start with 1,000 free credits. No credit card required 1,000 free API credits Anti-bot bypass included [Start Free](https://scrapfly.io/register) [View Docs](https://scrapfly.io/docs/onboarding) Not ready? Get our newsletter instead. ## Explore this Article with AI [ ChatGPT ](https://chat.openai.com/?q=Summarize%20this%20page%3A%20https%3A%2F%2Fscrapfly.io%2Fblog%2Fposts%2Fguide-to-javascript-axios-headers) [ Gemini ](https://www.google.com/search?udm=50&aep=11&q=Summarize%20this%20page%3A%20https%3A%2F%2Fscrapfly.io%2Fblog%2Fposts%2Fguide-to-javascript-axios-headers) [ Grok ](https://x.com/i/grok?text=Summarize%20this%20page%3A%20https%3A%2F%2Fscrapfly.io%2Fblog%2Fposts%2Fguide-to-javascript-axios-headers) [ Perplexity ](https://www.perplexity.ai/search/new?q=Summarize%20this%20page%3A%20https%3A%2F%2Fscrapfly.io%2Fblog%2Fposts%2Fguide-to-javascript-axios-headers) [ Claude ](https://claude.ai/new?q=Summarize%20this%20page%3A%20https%3A%2F%2Fscrapfly.io%2Fblog%2Fposts%2Fguide-to-javascript-axios-headers) ## Related Articles [ curl ### How to Use cURL GET Requests Here's everything you need to know about cURL GET requests and some common pitfalls you should avoid. ](https://scrapfly.io/blog/posts/how-to-use-curl-get-requests) [ http python ### Guide to Python requests POST method Discover how to use Python's requests library for POST requests, including JSON, form data, and file uploads, along with... ](https://scrapfly.io/blog/posts/how-to-python-requests-post) [ http blocking ### Post-Quantum TLS: Why Scraping Tools Are Now Exposed Post-quantum TLS is now a live bot detection signal. Modern browsers send X25519MLKEM768 key shares by default, and scra... ](https://scrapfly.io/blog/posts/post-quantum-tls-bot-detection) ## Related Questions - [ Q How to Use cURL Config Files? ](https://scrapfly.io/blog/answers/how-to-set-curl-config-file) - [ Q How to use proxies with NodeJS axios? ](https://scrapfly.io/blog/answers/how-to-use-proxies-nodejs-axios) - [ Q How To Send cURL POST Requests? ](https://scrapfly.io/blog/answers/how-to-send-a-post-request-using-curl) - [ Q How to Set User Agent With cURL? ](https://scrapfly.io/blog/answers/how-to-set-curl-user-agent) Scale your web scraping effortlessly, **1,000 free credits** [Start Free](https://scrapfly.io/register)