gfal-ls seems happy with the response, although it's unhappy with the ctime:
That's interesting!
Here we go, first the client side:
$ davix-ls -P Grid https://xrootd006.physik.uni-bonn.de:1094/cephfs/grid/atlas/atlaslocalgroupdisk/space-usage.json
(Davix::HttpRequest) Error: HTTP 404 : File not found
In parallel, on the server:
180523 19:59:22 154472 ofs_opendir: /C=DE/O=.3268:[log in to unmask] Unable to open directory /cephfs/grid/atlas/atlaslocalgroupdisk/space-usage.json; not a directory
Now with gfal-ls:
$ gfal-ls -l https://xrootd006.physik.uni-bonn.de:1094/cephfs/grid/atlas/atlaslocalgroupdisk/space-usage.json
-rwxr-xr-x 0 0 0 321 Jan 1 1970 https://xrootd006.physik.uni-bonn.de:1094/cephfs/grid/atlas/atlaslocalgroupdisk/space-usage.json
So the issue occurs with davix-ls only.
However, if I check with debug information:
$ gfal-ls -vvv -l https://xrootd006.physik.uni-bonn.de:1094/cephfs/grid/atlas/atlaslocalgroupdisk/space-usage.json
[...]
DEBUG Davix: > HEAD /cephfs/grid/atlas/atlaslocalgroupdisk/space-usage.json HTTP/1.1
[...]
And with davix-ls:
$ davix-ls -P Grid https://xrootd006.physik.uni-bonn.de:1094/cephfs/grid/atlas/atlaslocalgroupdisk/space-usage.json
[...]
> PROPFIND /cephfs/grid/atlas/atlaslocalgroupdisk/space-usage.json?xrdhttptk=REDACTED HTTP/1.1
> User-Agent: libdavix/0.6.7 neon/0.0.29
> Keep-Alive:
> Connection: Keep-Alive
> TE: trailers
> Host: [::ffff:131.220.166.120]:1094
> Depth: 1
> Content-Length: 303
>
[...]
- The first observation is that
gfal-ls uses HEAD and not PROPFIND.
- The second observation is that you got
PROPFIND to work fine with curl - could you share your commandline to be used with a VOMS proxy?
- The third observation is the difference in headers. My hunch is that
Depth: 1 is causing the issue.
My hunch in (3) is also supported by the fact that also the nagios-script at https://gitlab.cern.ch/lcgdm/nagios-plugins-webdav/blob/master/src/check_webdav#L710 uses Depth: 1 and fails, too.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.
{"@context":"http://schema.org","@type":"EmailMessage","potentialAction":{"@type":"ViewAction","target":"https://github.com/xrootd/xrootd/issues/691#issuecomment-391444417","url":"https://github.com/xrootd/xrootd/issues/691#issuecomment-391444417","name":"View Issue"},"description":"View this Issue on GitHub","publisher":{"@type":"Organization","name":"GitHub","url":"https://github.com"}}
{"api_version":"1.0","publisher":{"api_key":"05dde50f1d1a384dd78767c55493e4bb","name":"GitHub"},"entity":{"external_key":"github/xrootd/xrootd","title":"xrootd/xrootd","subtitle":"GitHub repository","main_image_url":"https://cloud.githubusercontent.com/assets/143418/17495839/a5054eac-5d88-11e6-95fc-7290892c7bb5.png","avatar_image_url":"https://cloud.githubusercontent.com/assets/143418/15842166/7c72db34-2c0b-11e6-9aed-b52498112777.png","action":{"name":"Open in GitHub","url":"https://github.com/xrootd/xrootd"}},"updates":{"snippets":[{"icon":"PERSON","message":"@olifre in #691: \u003e gfal-ls seems happy with the response, although it's unhappy with the ctime:\r\n\r\nThat's interesting!\r\n\r\nHere we go, first the client side:\r\n```\r\n$ davix-ls -P Grid https://xrootd006.physik.uni-bonn.de:1094/cephfs/grid/atlas/atlaslocalgroupdisk/space-usage.json \r\n(Davix::HttpRequest) Error: HTTP 404 : File not found \r\n```\r\nIn parallel, on the server:\r\n```\r\n180523 19:59:22 154472 ofs_opendir: /C=DE/O=.3268:[log in to unmask] Unable to open directory /cephfs/grid/atlas/atlaslocalgroupdisk/space-usage.json; not a directory\r\n```\r\n\r\nNow with `gfal-ls`:\r\n```\r\n$ gfal-ls -l https://xrootd006.physik.uni-bonn.de:1094/cephfs/grid/atlas/atlaslocalgroupdisk/space-usage.json \r\n-rwxr-xr-x 0 0 0 321 Jan 1 1970 https://xrootd006.physik.uni-bonn.de:1094/cephfs/grid/atlas/atlaslocalgroupdisk/space-usage.json\r\n```\r\nSo the issue occurs with `davix-ls` only. \r\n\r\nHowever, if I check with debug information:\r\n```\r\n$ gfal-ls -vvv -l https://xrootd006.physik.uni-bonn.de:1094/cephfs/grid/atlas/atlaslocalgroupdisk/space-usage.json\r\n[...]\r\nDEBUG Davix: \u003e HEAD /cephfs/grid/atlas/atlaslocalgroupdisk/space-usage.json HTTP/1.1\r\n[...]\r\n```\r\nAnd with `davix-ls`:\r\n```\r\n$ davix-ls -P Grid https://xrootd006.physik.uni-bonn.de:1094/cephfs/grid/atlas/atlaslocalgroupdisk/space-usage.json\r\n[...]\r\n\u003e PROPFIND /cephfs/grid/atlas/atlaslocalgroupdisk/space-usage.json?xrdhttptk=REDACTED HTTP/1.1\r\n\u003e User-Agent: libdavix/0.6.7 neon/0.0.29\r\n\u003e Keep-Alive: \r\n\u003e Connection: Keep-Alive\r\n\u003e TE: trailers\r\n\u003e Host: [::ffff:131.220.166.120]:1094\r\n\u003e Depth: 1\r\n\u003e Content-Length: 303\r\n\u003e \r\n[...]\r\n```\r\n\r\n1. The first observation is that `gfal-ls` uses `HEAD` and not `PROPFIND`. \r\n2. The second observation is that you got `PROPFIND` to work fine with `curl` - could you share your commandline to be used with a VOMS proxy?\r\n3. The third observation is the difference in headers. My hunch is that `Depth: 1` is causing the issue. \r\n\r\nMy hunch in (3) is also supported by the fact that also the nagios-script at https://gitlab.cern.ch/lcgdm/nagios-plugins-webdav/blob/master/src/check_webdav#L710 uses `Depth: 1` and fails, too. "}],"action":{"name":"View Issue","url":"https://github.com/xrootd/xrootd/issues/691#issuecomment-391444417"}}}
{
"@type": "MessageCard",
"@context": "http://schema.org/extensions",
"hideOriginalBody": "false",
"originator": "37567f93-e2a7-4e2a-ad37-a9160fc62647",
"title": "Re: [xrootd/xrootd] (HTTP) PROPFIND on files fails with 404 (#691)",
"sections": [
{
"text": "",
"activityTitle": "**Oliver Freyermuth**",
"activityImage": "https://avatars2.githubusercontent.com/u/166759?s=160\u0026v=4",
"activitySubtitle": "@olifre",
"facts": [
]
}
],
"potentialAction": [
{
"name": "Add a comment",
"@type": "ActionCard",
"inputs": [
{
"isMultiLine": true,
"@type": "TextInput",
"id": "IssueComment",
"isRequired": false
}
],
"actions": [
{
"name": "Comment",
"@type": "HttpPOST",
"target": "https://api.github.com",
"body": "{\n\"commandName\": \"IssueComment\",\n\"repositoryFullName\": \"xrootd/xrootd\",\n\"issueId\": 691,\n\"IssueComment\": \"{{IssueComment.value}}\"\n}"
}
]
},
{
"name": "Close issue",
"@type": "HttpPOST",
"target": "https://api.github.com",
"body": "{\n\"commandName\": \"IssueClose\",\n\"repositoryFullName\": \"xrootd/xrootd\",\n\"issueId\": 691\n}"
},
{
"targets": [
{
"os": "default",
"uri": "https://github.com/xrootd/xrootd/issues/691#issuecomment-391444417"
}
],
"@type": "OpenUri",
"name": "View on GitHub"
},
{
"name": "Unsubscribe",
"@type": "HttpPOST",
"target": "https://api.github.com",
"body": "{\n\"commandName\": \"MuteNotification\",\n\"threadId\": 327319225\n}"
}
],
"themeColor": "26292E"
}
Use REPLY-ALL to reply to list
To unsubscribe from the XROOTD-DEV list, click the following link:
https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=XROOTD-DEV&A=1
