Skip to content

docs: document frontend.allowed.client.origins CORS property - #8204

Closed
dcache-ci wants to merge 2 commits into
masterfrom
frontend-cors
Closed

docs: document frontend.allowed.client.origins CORS property#8204
dcache-ci wants to merge 2 commits into
masterfrom
frontend-cors

Conversation

@dcache-ci

Copy link
Copy Markdown

The frontend service now supports Cross-Origin Resource Sharing (CORS) controlled by the new frontend.allowed.client.origins property.

This documentation update describes how site administrators can allow third-party web applications (e.g. data catalogs) to call the dCache REST API from the browser.

kofemann and others added 2 commits August 20, 2026 15:56
Motivation:
dcache's REST API can be integrated into various web application such as
data catalogs. For seamless integration dCache should provide the
allowedOrigins header.

Modification:
move CrossOriginResourceSharingHandler class from webdav into util/jetty
directory. Update frontend.xml to include CrossOriginResourceSharingHandler
in the jetty handler list. Introduce property
`frontend.allowed.client.origins` to control allowed origins.

Result:
frontend can be called from third-party javascript applications if
allowed.

Acked-by:
Target: master
Require-book: no
Require-notes: yes
The frontend now supports Cross-Origin Resource Sharing (CORS) via the
new frontend.allowed.client.origins property. Document how site
administrators can allow third-party web applications to call the
dcache REST API.
@kofemann kofemann closed this Sep 10, 2026
@kofemann
kofemann deleted the frontend-cors branch September 10, 2026 10:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants