As reported in a HIFIS ticket: https://support.hifis.net/#ticket/zoom/12959/74167
A user reported seeing a HEAD request returning a 200 status code on a HEAD request:
curl -I -H "Range: bytes=0-1023" https://dcache-doma-door01.desy.de/Helmholtz/HIP/collaborations/PixelPatrol/WHOI.parquet
However, my tests show that a GET request returns the expected 206 status code:
paul@celebrimbor:~$ curl -s -D- --output /dev/null -H "Range: bytes=0-1023" https://dcache-doma-door01.desy.de/Helmholtz/HIP/collaborations/PixelPatrol/WHOI.parquet
HTTP/1.1 206 Partial Content
Date: Fri, 17 Apr 2026 15:32:45 GMT
Server: dCache/9.2.35
Content-Range: bytes 0-1023/1681405279
ETag: "00003044946DE73B4FE984C47F41B9C1CAA8_-1867312900"
Content-Disposition: attachment
Content-Length: 1024
paul@celebrimbor:~$
Since a HEAD and GET request for the same URL should return the same status code, I believe this behaviour is a bug in dCache.
As reported in a HIFIS ticket: https://support.hifis.net/#ticket/zoom/12959/74167
A user reported seeing a HEAD request returning a 200 status code on a HEAD request:
However, my tests show that a GET request returns the expected 206 status code:
Since a HEAD and GET request for the same URL should return the same status code, I believe this behaviour is a bug in dCache.