Doc: AWS S3 CORS configuration #208
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
tejaswinichile
force-pushed
the
doc/207-s3-cors-config
branch
from
7ce4200 to
c27b7a5
Compare
pranavrajs
reviewed
Mar 4, 2022
|
|
||
|  | ||
|
|
||
| So for self-hosted version, you have your widget on https://www.example-site.com and your chatwoot dashboard on https://www.app.example-site.com the these both will be in AllowedOrigin array, it will look like below. |
There was a problem hiding this comment.
@tejaswinichile Does this mean that if the user has deployed the widget on for eg: google.com and the app is hosted on app.chatwoot.com, then do we need both URLs to be whitelisted here?
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fix: #207