Paul Millar

Hi @mzur, Thanks for reporting this problem. DESY actually runs multiple dCache instances, each tailored for specific user community. From the context, I believe you're using the [dCache InfiniteSpace service](https://helmholtz.cloud/services/?serviceID=9b6c63a4-d26b-4ea6-b8b0-88c0be5ea610)....

Hi @dgarijo, This is a pattern we've used in other maven projects. Forgive me if I'm saying stuff you already know .... The goal is that all non-release builds will...

The problem here is that `null` is a valid value for `FileAttribute.QOS_POLICY`. Writing `attributes.setQosPolicy(null);` is valid. However, `null` is _not_ a valid value to be encapsulated within `Optional`. Philosophically, there...

Hi @airnandez , Although I'm spending less time working on dCache these days, perhaps I can add some context here that might be useful. dCache's WebDAV support comes from an...

Hi @airnandez, The `PUT`/`DELETE` on an empty file is a clever trick, although I agree it's unsatisfactory. A few thoughts: - Do you need to create empty directories? Otherwise, wouldn't...

Some comments: - I believe corrupted data most often comes from an incomplete upload, but there are other causes (e.g., inconsistency between file storage and a catalogue, silent corruption, damaged...

OK, hopefully to clarify ... The "In the case of corrupt data, the file may still have value" comment was meant as a general statement. One might have transferred some...

Hi @labkode Thanks for all your work in this area. As I'm sure you already know, dCache already implements integrity checking when undertaking HTTP-TPC transfers. There are a few points...

Just to add, there's [a nice example from MDN](https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Status/413#examples) that describes a use for `413` status code when the user has exceeded their file upload limit. This seems directly applicable...