Rob Wu

I think that a `proxyBasePath` option that defaults to `/` would make sense. Then the "/" should be removed here: https://github.com/Rob--W/cors-anywhere/blob/143eff177c7e7d4bf241b83c57dd1e2c6378d53b/lib/cors-anywhere.js#L191 Do you want to submit a PR?

If you don't mind using a different port, just start listening on 0.0.0.0 and your specific port. If you really insist on hosting CORS Anywhere at a subpath of your...

> to avoid security issues in production, since we're using it in a development server we would like to allow it. This line of thinking is dangerous ;) Adding such...

> Need to include the cookie in the CORS request. I tried adding with credential="true" command in my request but with that cookie is not going through the cors request....

@jeetgit See https://github.com/Rob--W/cors-anywhere/issues/56#issuecomment-267905416 to see what to change, and where to change it.

Can you show an example of how you are using CORS Anywhere in this way?

CORS Anywhere is not supposed to be used as a generic proxy. In particular, it does not attempt to modify response bodies. If you wish to "proxy everything", you have...

Change it from where? Have you tried the `setHeaders` option (see README)?

This issue is caused by an incorrectly configured server (orcid.org). When orcid.org is accessed over https, it redirects to http. This is bad security practice, but it is quite common....

What do you mean by "getting the server to work in a subdirectory?"