Skip to content
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

fix(dgw): allow any header to be set in browser JavaScript HTTP requests #1083

Merged
merged 2 commits into from
Oct 31, 2024

Conversation

CBenoit
Copy link
Member

@CBenoit CBenoit commented Oct 31, 2024

We don’t expose any header particularly sensitive from the Devolutions Gateway, and the future HTTP bridge will always require a token which is only issued on a per need basis. In fact, in such cases we actually want to allow virtually any header to be used for web-based integration of various web services (e.g.: VMware dashboard).
The restriction imposed by the token requirement is strong enough.

We don’t expose any header particularly sensitive from the Devolutions
Gateway, and the future HTTP bridge will always require a token which
is only issued on a per need basis. In fact, in such cases we actually
want to allow virtually any header to be used for web-based integration
of various web services (e.g.: VMware dashboard).
The restriction imposed by the token requirement is strong enough.
@CBenoit CBenoit enabled auto-merge (squash) October 31, 2024 09:21
@CBenoit CBenoit merged commit 0a7c808 into master Oct 31, 2024
26 checks passed
@CBenoit CBenoit deleted the fix/cors-allow-any-header branch October 31, 2024 17:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

2 participants