-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
KnotxServer response configuration #41
Comments
Currently it doesn't work like that. Within Server Configuration. Solution from |
This issue is still valid for |
6 tasks
dragarthPl
added a commit
to dragarthPl/knotx-commons
that referenced
this issue
Feb 14, 2020
dragarthPl
added a commit
to dragarthPl/knotx-server-http
that referenced
this issue
Feb 14, 2020
This was referenced Feb 14, 2020
dragarthPl
added a commit
to dragarthPl/knotx-server-http
that referenced
this issue
Feb 14, 2020
dragarthPl
added a commit
to dragarthPl/knotx-server-http
that referenced
this issue
Feb 16, 2020
dragarthPl
added a commit
to dragarthPl/knotx-server-http
that referenced
this issue
Feb 19, 2020
dragarthPl
added a commit
to dragarthPl/knotx-server-http
that referenced
this issue
Feb 19, 2020
malaskowski
pushed a commit
that referenced
this issue
Feb 21, 2020
[#41]KnotxServer response configuration - wildcards
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Should setting "allowedResponseHeaders" to wildcard result in all headers being allowed?
This approach works in "allowedRequestHeaders" section of HttpRepositoryConnector configuration.
Example:
"knotx:io.knotx.KnotxServer": { "options": { "config": { "allowedResponseHeaders": [ "*" ], ... } } }
The text was updated successfully, but these errors were encountered: