-
Notifications
You must be signed in to change notification settings - Fork 5
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
Using the right WebDAV door, revisited #250
Comments
I'm actually just discovering a similar problem for a dCache instance here at DESY. The cause is that dCacheView has a hard-coded tag it uses to selected WebDAV doors: Only if there are no doors with this tag (and that have a door-root path of If that configuration property isn't defined then it uses the same endpoint as frontend, but with port 2880. So, currently the only way to have different dCacheView / frontend target different WebDAV endpoints is to make sure the |
Hi Paul, thanks for your reply. Then I must have misunderstood this property:
Or is it not fully implemented yet? And I thought I had removed the "dcache-view" tag from all WebDAV doors, but I guess I must have missed some. I'll check. Cheers, |
The We don't have a property to say which tag frontend will use to select webdav doors -- that's really the problem :-( |
It appears I had removed all the "dcache-view" tags after all:
Assuming it's still "dcache-view". So then the frontend.static!dcache-view.endpoints.webdav values should be used, which would be OK, if it worked. |
I did a little digging and although Femi fixed #231 in dCacheView, there was no release of dCacheView with that bug-fix, and therefore no fix in dCache. I've another couple of fixes that are also ready to go into dCache (#244 & #245). These are also committed. I plan to do a release of dCacheView now and request dCache is updated to use that new version. That new version dCacheView (that would come along with a new version of dCache) may be sufficient to get something working, albeit not in a great way. I'll also try to fix #251 and #252, which should make handling multiple frontend/dCacheView instances easier to deploy. |
This probably a follow-up of #231, but I'm not quite sure so I opened a new ticket.
I have 4 flavors of dCacheView and I want each of them to point to a dedicated WebDAV door by using tags. However, I can't seem to get it working.
The layout file:
I log in to the dCacheView on port 22880 (username/password) and go to a file; then I try to download the file but dCacheView says "TypeError: Request failed with response status code 404." In the Firefox browser console I can see this error:
XHR GET https://dcacheview.grid.surfsara.nl:22881/scripts/tasks/undefined
The "undefined" looks similar to #231.
We're running 6.0.29.
The text was updated successfully, but these errors were encountered: