explicitly require content-type and content-length

This commit is contained in:
hzrd149
2025-06-17 15:00:33 -05:00
parent 620d74c2a2
commit 977d0be083

View File

@@ -131,9 +131,9 @@ Example event for retrieving multiple blobs from single server:
## HEAD /sha256 - Has Blob ## HEAD /sha256 - Has Blob
The `HEAD /<sha256>` endpoint MUST be identical to the `GET /<sha256>` endpoint except that it MUST NOT return the blob in the reponse body per [RFC 7231](https://www.rfc-editor.org/rfc/rfc7231#section-4.3.2) The `HEAD /<sha256>` endpoint SHOULD be identical to the `GET /<sha256>` endpoint except that it MUST NOT return the blob in the reponse body per [RFC 7231](https://www.rfc-editor.org/rfc/rfc7231#section-4.3.2)
The endpoint MUST respond with the same headers that the `GET /<sha256>` endpoint would respond with including the `Content-Type` header and other content headers. The endpoint MUST respond with the same `Content-Type` and `Content-Length` headers as the `GET /<sha256>` endpoint.
The endpoint MUST accept an optional file extension in the URL similar to the `GET /<sha256>` endpoint. ie. `.pdf`, `.png`, etc The endpoint MUST accept an optional file extension in the URL similar to the `GET /<sha256>` endpoint. ie. `.pdf`, `.png`, etc