refactor: enable CORS for GET /setting/application#390
Merged
Conversation
The Easysearch UI needs to call /setting/application on the Agent to discover provider configuration and to link an Easysearch node back to the Agent that launched it. When the UI is served from a different origin, browsers block these cross-origin requests because the endpoint did not return CORS headers. Enable CORS for the GET /setting/application endpoint so the Agent can respond with the correct Access-Control-Allow-Origin and allowed headers.
SteveLauC
changed the title
medcl
approved these changes
Jul 9, 2026
hardy-dev-infinilabs
approved these changes
Jul 9, 2026
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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.
The Easysearch UI needs to call /setting/application on the Agent to discover the agent/provider configuration and to link an Easysearch node back to its managing agent. Without CORS headers, browsers block these cross-origin requests when the UI is served from a different host/port.
Add the CORS feature flag to the GET /setting/application endpoint so the agent can respond with the appropriate Access-Control-Allow-Origin and allowed headers.
Standards checklist