Rob Wu
@Shahrukh95 The error message suggests that you're requesting the URL via `httpS://localhost:8081/`, but that the (proxy) server does not support `httpS`. Either add https support (by configuring a certificate as...
There is not enough information here for me to help. Somewhere, a server is clearly generating 500 Internal Server Error. It's not CORS Anywhere itself, and according to you your...
CORS Anywhere relies on (undocumented) internals of the `http-proxy` library. Use a specific version instead of a version range to ensure that CORS Anywhere is guaranteed to work. Look for...
You have something else running in front of CORS Anywhere that normalizes the URLs. You should disable that URL rewriting mechanism, to preserve the original request URL. If that is...
The typical use case is to access a public resource that is not available due to the lack of CORS headers. As the operator of the server, the main risks...
> Regarding the xfwd header, it seems pretty useful and would be nice to just enable it in the options. Could we add this as a feature? > My use...
Yes, if you use CORS Anywhere as a server-side library, then you can use the `setHeaders` option to add request headers. Documentation: https://github.com/Rob--W/cors-anywhere#server Example: https://github.com/Rob--W/cors-anywhere/blob/4814647a9d21f14858da282387a4295c17f2851d/test/test.js#L818-L847
Do you mean **request** headers or **response** headers? In either case, CORS Anywhere does not have out-of-the-box support for domain-specific headers (request headers / response headers). If you want to...
> I tried to use **setHeaders** in the server for the "origin" and "referer' headers, but they seem not to change as they are both still https://localhost:port instead of the...
Are you sending a request from a web page at the same origin? If so (and the answer is most likely yes because of the absence of the `Origin` request...