We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
500 server error
Dear dCache devs,
This is a minor thingy, but perhaps it's easy to fix.
When quota is reached, WebDAV doors sometimes return a clear error message:
[onno@ui ~]# curl --location --upload-file testfile https://dcachetest.grid.surfsara.nl:2881/users/onno/disk/quota4 Internal problem: REPLICA user quota exceeded for uid=99999
But with curl --fail, the error is quite different and confusing:
curl --fail
[onno@ui ~]# curl --fail --location --upload-file testfile https://dcachetest.grid.surfsara.nl:2881/users/onno/disk/quota curl: (22) The requested URL returned error: 500 Server Error
The user might think that dCache is broken! Surely we don't want the user to think that? 😉
Wouldn't it be better if WebDAV returned this HTTP code?
507 Insufficient Storage (WebDAV; RFC 4918) The server is unable to store the representation needed to complete the request.
Another candidate might be "413 Payload Too Large".
Cheers, Onno
The text was updated successfully, but these errors were encountered:
Hi Onno,
When it rains in pours. We just had similar complain at Fermilab. Yes, we will implement 507 return code shortly.
Sorry, something went wrong.
DmitryLitvintsev
No branches or pull requests
Dear dCache devs,
This is a minor thingy, but perhaps it's easy to fix.
When quota is reached, WebDAV doors sometimes return a clear error message:
But with
curl --fail
, the error is quite different and confusing:The user might think that dCache is broken! Surely we don't want the user to think that? 😉
Wouldn't it be better if WebDAV returned this HTTP code?
Another candidate might be "413 Payload Too Large".
Cheers,
Onno
The text was updated successfully, but these errors were encountered: