# \#nginx

**URL:** https://forum.openreplay.com/tag/nginx/117.md

[Latest](https://forum.openreplay.com/latest.md) · [Categories](https://forum.openreplay.com/categories.md) · [Tags](https://forum.openreplay.com/tags.md)

---

## [Is the X-Openreplay-Batch a new mandatory header?](https://forum.openreplay.com/t/is-the-x-openreplay-batch-a-new-mandatory-header/76)

<div class="topic-metadata">

**Author:** [@dave-the-developer](https://forum.openreplay.com/u/dave-the-developer)\
**Replies:** 1\
**Last updated:** [April 11, 2024, 2:32pm UTC](https://forum.openreplay.com/t/is-the-x-openreplay-batch-a-new-mandatory-header/76 "2024-04-11T14:32:14Z")

</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.