# Is it correct to response to HEAD req from elastic API with empty "transfer-encoding: chunked"?

**URL:** <https://discuss.elastic.co/t/is-it-correct-to-response-to-head-req-from-elastic-api-with-empty-transfer-encoding-chunked/372941>\
**Category:** Elasticsearch\
**Created:** [January 8, 2025, 3:06pm UTC](https://discuss.elastic.co/t/is-it-correct-to-response-to-head-req-from-elastic-api-with-empty-transfer-encoding-chunked/372941 "2025-01-08T15:06:11Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![DavidTurner](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/davidturner/32/22453_2.png) [@DavidTurner](https://discuss.elastic.co/u/DavidTurner)\
**Post date:** [January 13, 2025, 9:20am UTC](https://discuss.elastic.co/t/is-it-correct-to-response-to-head-req-from-elastic-api-with-empty-transfer-encoding-chunked/372941/4 "2025-01-13T09:20:05Z")

</div>

No, that's not the case. HEAD requests are special in this regard. See e.g. [RFC 9112 §6.3](https://www.rfc-editor.org/rfc/rfc9112#message.body.length):

> 1. Any response to a HEAD request [...] is always terminated by the first empty line after the header fields, **regardless of the header fields present in the message** , [...]

---

_[View the full topic](https://discuss.elastic.co/t/is-it-correct-to-response-to-head-req-from-elastic-api-with-empty-transfer-encoding-chunked/372941)._