# Is the X-Openreplay-Batch a new mandatory header?

**URL:** <https://forum.openreplay.com/t/is-the-x-openreplay-batch-a-new-mandatory-header/76>\
**Category:** 🛠️ Deployment\
**Tags:** nginx, tracker\
**Created:** [April 11, 2024, 2:30pm UTC](https://forum.openreplay.com/t/is-the-x-openreplay-batch-a-new-mandatory-header/76 "2024-04-11T14:30:24Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![dave-the-developer](https://avatars.discourse-cdn.com/v4/letter/d/7ab992/32.png) [@dave-the-developer](https://forum.openreplay.com/u/dave-the-developer)\
**Post date:** [April 11, 2024, 2:30pm UTC](https://forum.openreplay.com/t/is-the-x-openreplay-batch-a-new-mandatory-header/76/1 "2024-04-11T14:30:24Z")

</div>

Is `X-Openreplay-Batch:` a new header that has to be allowed? I just did the upgrade and now my ingest POSTs are failing due to CORS’ Access-Control-Allow-Headers not including it.

---

<div class="post-metadata">

**Author:** ![mehdi](https://dub1.discourse-cdn.com/flex006/user_avatar/forum.openreplay.com/mehdi/32/50_2.png) [@mehdi](https://forum.openreplay.com/u/mehdi)\
**Post date:** [April 11, 2024, 2:32pm UTC](https://forum.openreplay.com/t/is-the-x-openreplay-batch-a-new-mandatory-header/76/2 "2024-04-11T14:32:14Z")

</div>

This header is not used anymore. Simply update the tracker version to latest and that’ll solve the problem.