am(cors): domain level CORS doc #1010
Open
Conversation
This file contains 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
|
Kudos, SonarCloud Quality Gate passed!
|
| = CORS Configuration | ||
| :page-sidebar: am_3_x_sidebar | ||
| :page-permalink: am/current/am_userguide_cors_configuration.html | ||
| :page-folder: am/user-guide |
There was a problem hiding this comment.
Suggested change
| :page-folder: am/user-guide | |
| :page-folder: am/user-guide |
| === Access-Control-Allow-Origin | ||
|
|
||
| Allow to specify one or multiples origin(s) that may access the resource. | ||
| If you want to allow all origins, you can put `*` but it's not safe for production. |
There was a problem hiding this comment.
Suggested change
| If you want to allow all origins, you can put `*` but it's not safe for production. | |
| If you want to allow all origins, you can put `*` but this is not safe for production. |
| Here you specify the headers allowed to be used by your requests. | ||
| Typically, on your request headers you will have a header `Access-Control-Request-Headers` which request CORS to be configured to allow its values. | ||
|
|
||
| Let's see a simple use case: |
There was a problem hiding this comment.
Suggested change
| Let's see a simple use case: | |
| ==== Simple use case |
|
|
||
| Here is the screenshot of these variables from the `gravitee.yml` file | ||
|
|
||
| image::{% link images/am/current/graviteeio-am-userguide-cors-settings-yml.png %}[Gateway CORS defailt settings,500,400] |
There was a problem hiding this comment.
Why use a screenshot (which I find difficult to read) when you could just copy and paste an example directly from the gravitee.yml file?
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This documentation is for 3.21.x domain level CORS configuration
🚀 CI was able to deploy the build of this PR, so you can now try it directly here