Some services that MavenWorks interacts with will inevitably have incorrect CORS headers or straight-up not allow CORS requests. To sidestep this, we need to setup a proxy to allow these sorts of requests to go through.
This should be off-by-default, since it defeats CORS/CSP and could thus introduce a security hole. It should also use a whitelist to restrict the origins that can be proxied, for the same reason.
Some services that MavenWorks interacts with will inevitably have incorrect CORS headers or straight-up not allow CORS requests. To sidestep this, we need to setup a proxy to allow these sorts of requests to go through.
This should be off-by-default, since it defeats CORS/CSP and could thus introduce a security hole. It should also use a whitelist to restrict the origins that can be proxied, for the same reason.