Header Сontent-Type is missing for request: HEAD /objects/{containerId}/by_id/{objectId} #86

New issue

Closed

opened 2025-12-28 18:00:06 +00:00 by sami · 0 comments

sami commented

2025-12-28 18:00:06 +00:00

Owner

Originally created by @mike-petrov on GitHub (Aug 9, 2024).

Originally assigned to: @tatiana-nspcc on GitHub.

Current Behavior

If we use GET /objects/{containerId}/by_id/{objectId}, we can see Сontent-Type header:

but if we use HEAD /objects/{containerId}/by_id/{objectId} for the same object, we can't see header:

Expected Behavior

like GET requset

Your Environment

Version of the product used: v0.9.0
Server setup and configuration files used: rest.t5.fs.neo.org/v1/docs

Originally created by @mike-petrov on GitHub (Aug 9, 2024). Originally assigned to: @tatiana-nspcc on GitHub. ## Current Behavior If we use `GET /objects/{containerId}/by_id/{objectId}`, we can see `Сontent-Type` header: <img width="300" alt="image" src="https://github.com/user-attachments/assets/914478e9-f514-4d02-9a5b-5a08bc716c0e"> but if we use `HEAD /objects/{containerId}/by_id/{objectId}` for the same object, we can't see header: <img width="300" alt="image" src="https://github.com/user-attachments/assets/cd24dc1f-da49-4c5d-a3fd-694ffcdd56d1"> ## Expected Behavior like GET requset ## Your Environment * Version of the product used: v0.9.0 * Server setup and configuration files used: [rest.t5.fs.neo.org/v1/docs](https://rest.t5.fs.neo.org/v1/docs/)