Remove requestFromBrowser settings from docs and config

There is an old field from the Meteor version which seems to be left over in the docs and config files:

https://github.com/OHIF/Viewers/search?q=requestFromBrowser&unscoped_q=requestFromBrowser

Remove requestFromBrowser from all files. If it is the only field in the object requestOptions, remove the entire object from the config object.

[dannyrb]

If the web client makes web request to a PACS located at a different host/domain, you will need to address CORS

[dannyrb]

Correct. With v1 you could proxy requests to the PACs and avoid CORS errors. We don’t have a way to sidestep this issue now that the OHIF Viewer doesn’t have a server side component.

Most PACS do not recommend exposure to the open web. You can see how we use nginx to reverse proxy requests in one of our deployment recipes – most web servers support this feature. In our recipe, because the DICOMWeb endpoints and the web client share the same origin, no CORS headers are needed.

We’re aware that CORS is a common pain point for our users. It’s a bit tricky, as there’s no good silver bullet for all of the potential setups, and we’re trying to avoid the maintenance burden (and security issues) a proxy can cause. Even education is a bit difficult as the bulk of our users have limited experience with stuff like this.

If you have any recommendations, we’re definitely all ears. As is, I point people to our recipes and hint that they may need to reach out to a consultancy.