8000 Old UI not working with AllowEncodedSlashes NoDecode · Issue #7724 · rucio/rucio · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Old UI not working with AllowEncodedSlashes NoDecode #7724

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

Open
lobis opened this issue May 14, 2025 · 1 comment · May be fixed by #7725
Open

Old UI not working with AllowEncodedSlashes NoDecode #7724

lobis opened this issue May 14, 2025 · 1 comment · May be fixed by #7725
Assignees

Comments

@lobis
Copy link
Contributor
lobis commented May 14, 2025

Related:

rucio/containers#402

@maany
Copy link
Member
maany commented May 14, 2025

Adding more context here:

The old UI has a single file called rucio.js that acts as a rucio HTTP client. It makes requests to the UI's /proxy endpoint, which relays the request to the configured rucio server.

What Luis introduced in this containers PR, is way to to set the AllowEncodedSlashes directive in the apache that sits in front of the UI.

As a second step, we need to encode the URLs in the rucio.js and send it to the UI Proxy, which can forward it to the rucio server.

This issue is focused on the latter

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Development

Successfully merging a pull request may close this issue.

2 participants
0