diff options
author | Sascha Brockel <info@sascha-brockel.de> | 2022-02-21 22:04:51 +0100 |
---|---|---|
committer | GitHub <noreply@github.com> | 2022-02-21 22:04:51 +0100 |
commit | e4b077843caac86d161b095173fd804abf194bef (patch) | |
tree | 07af89d359293ce23b7e22368c80642264fbbf35 | |
parent | 5cd802d157a687224949a0f0cc9f93413aefaaf2 (diff) | |
download | homer-e4b077843caac86d161b095173fd804abf194bef.tar.gz homer-e4b077843caac86d161b095173fd804abf194bef.tar.zst homer-e4b077843caac86d161b095173fd804abf194bef.zip |
Fix typos in troubleshooting
-rw-r--r-- | docs/troubleshooting.md | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/docs/troubleshooting.md b/docs/troubleshooting.md index ed1f85d..649e5a6 100644 --- a/docs/troubleshooting.md +++ b/docs/troubleshooting.md | |||
@@ -6,7 +6,7 @@ You might by facing a [CORS](https://developer.mozilla.org/en-US/docs/Web/HTTP/C | |||
6 | It happens when the targeted service is hosted on a different domain or port. | 6 | It happens when the targeted service is hosted on a different domain or port. |
7 | Web browsers will not allow to fetch information from a different site without explicit permissions (the targeted service | 7 | Web browsers will not allow to fetch information from a different site without explicit permissions (the targeted service |
8 | must include a special `Access-Control-Allow-Origin: *` HTTP headers). | 8 | must include a special `Access-Control-Allow-Origin: *` HTTP headers). |
9 | If this happens your web console (`ctrl+shit+i` or `F12`) will be filled with this kind of errors: | 9 | If this happens your web console (`ctrl+shift+i` or `F12`) will be filled with this kind of errors: |
10 | 10 | ||
11 | ```text | 11 | ```text |
12 | Access to fetch at 'https://<target-service>' from origin 'https://<homer>' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource. If an opaque response serves your needs, set the request's mode to 'no-cors' to fetch the resource with CORS disabled. | 12 | Access to fetch at 'https://<target-service>' from origin 'https://<homer>' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource. If an opaque response serves your needs, set the request's mode to 'no-cors' to fetch the resource with CORS disabled. |
@@ -15,5 +15,5 @@ Access to fetch at 'https://<target-service>' from origin 'https://<homer>' has | |||
15 | To resolve this, you can either: | 15 | To resolve this, you can either: |
16 | 16 | ||
17 | * Host all your target service under the same domain & port. | 17 | * Host all your target service under the same domain & port. |
18 | * Modify the target sever configuration so that the response of the server included following header- `Access-Control-Allow-Origin: *` (<https://developer.mozilla.org/en-US/docs/Web/HTTP/CORS#simple_requests>). It might be an option in the targeted service, otherwise depending on how the service is hosted, the proxy or web server can seamlessly add it. | 18 | * Modify the target server configuration so that the response of the server included following header- `Access-Control-Allow-Origin: *` (<https://developer.mozilla.org/en-US/docs/Web/HTTP/CORS#simple_requests>). It might be an option in the targeted service, otherwise depending on how the service is hosted, the proxy or web server can seamlessly add it. |
19 | * Use a cors proxy sever like [`cors-container`](https://github.com/imjacobclark/cors-container), [`cors-anywhere`](https://github.com/Rob--W/cors-anywhere) or many others. | 19 | * Use a cors proxy server like [`cors-container`](https://github.com/imjacobclark/cors-container), [`cors-anywhere`](https://github.com/Rob--W/cors-anywhere) or many others. |