fix: fixing errors in documentation (#2728)

Co-authored-by: Louis-Maxime Crédeville <louis-maxime.credeville@gleamer.ai>
This commit is contained in:
LumenolandLouis-Maxime Crédeville authored and GitHub committed 2022-03-03 11:28:07 -05:00
1 parent 6c9b5ca10c
commit fe9e7123d7
40 files changed
+77 -77

No files matched your search

+3 -3
View File
@@ -112,7 +112,7 @@ There are two important steps to making sure this setup works:
1. Your Image Archive needs to be exposed, in some way, to the open web. This
can be directly, or through a `reverse proxy`, but the Viewer needs _some
way_ to request it's data.
way_ to request its data.
2. \* Your Image Archive needs to have appropriate CORS (Cross-Origin Resource
Sharing) Headers
@@ -224,7 +224,7 @@ More info on this JSON format can be found here
_CORS Issues (Cross-Origin Resource Sharing)_
If you host a JSON API or Images on a different domain from the the app itself,
If you host a JSON API or Images on a different domain from the app itself,
you will likely have CORS issues. This will also happen when testing from
Localhost and reaching out to remote servers. Even if the domain is the same,
different ports, subdomains or protocols (https vs http) will also cause CORS
@@ -233,7 +233,7 @@ to allow your App server origin.
For example:
Lets assume your application is hosted on `https://my-ohif-server.com`.
Let's assume your application is hosted on `https://my-ohif-server.com`.
Your JSON API is hosted on `https://my-json-api.aws.com`