API
Corsfix provides two methods to proxy your requests, giving you flexibility in how you interact with the CORS Proxy.
Method 1: Direct URL Path
Section titled “Method 1: Direct URL Path”The simplest way to use the proxy is by appending the target URL directly to the path:
https://proxy.corsfix.com/?https://api.example.com/data
Example Usage
Section titled “Example Usage”fetch("https://proxy.corsfix.com/?https://api.example.com/data") .then((response) => response.json()) .then((data) => console.log(data));
Method 2: URL Parameter
Section titled “Method 2: URL Parameter”You can also use the url
parameter to specify your target:
https://proxy.corsfix.com/?url=https://api.example.com/data
Example Usage
Section titled “Example Usage”fetch("https://proxy.corsfix.com/?url=https://api.example.com/data") .then((response) => response.json()) .then((data) => console.log(data));
Request Headers
Section titled “Request Headers”Corsfix uses the Origin
header to validate if your application is authorized to use the CORS proxy. This header is automatically set when sending request from the browser, such as when using Fetch, Axios, or etc.
Response Headers
Section titled “Response Headers”The proxy automatically adds the following CORS header to the responses:
Access-Control-Allow-Origin: <your-request-origin>Access-Control-Expose-Headers: *
Timeouts
Section titled “Timeouts”When a request takes longer than 20 seconds to complete, the proxy will return a 504 Gateway Timeout
response. This status code indicates that the server did not receive a timely response from the target server.
Payload Size
Section titled “Payload Size”The maximum payload size for a request is 5MB. If your request exceeds this limit, the proxy will return a 413 Payload Too Large
response. This status code indicates that the request is larger than the allowed size.