Handle extension resources on server

[sandy081]

Handle extension resources on server

[alexdima]

Nice! I just left a couple of suggestions.

[monken]

What’s the rationale for this feature? It seems to create a completely open reverse proxy to any domain on the internet (and worse, the private networks that the server has access to). The browser handles cross origin request in a separate security context (which is what you want), this feature will effectively disable these safeguards.

[sandy081]

@monken Thanks for your feedback and very much appreciated. This is not targeting any server/domain in the internet. This is to redirect requests to the service (we are hosting) from the client to the server. We have strict CORS rules on this service of ours and its blocking the dev set up and testing. Instead of loosening the CORS rules (which is not ideal) we are redirecting these specific requests through server. Hope it is clear.

[sandy081]

Updated the PR to support following:

• Added a check on the server to validate if the URL is pointing to the target service or not.
• Selectively set request and response headers
• Client updates the protocol (http or https) of the URL correctly.

@alexdima @bpasero Please take a look at the changes.