# Cross-Origin Configuration

**URL:** <https://discuss.pomerium.com/t/cross-origin-configuration/384>\
**Category:** Support\
**Tags:** docker\
**Created:** [July 1, 2024, 6:36am UTC](https://discuss.pomerium.com/t/cross-origin-configuration/384 "2024-07-01T06:36:10Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![sorin.flueras](https://avatars.discourse-cdn.com/v4/letter/s/858c86/32.png) [@sorin.flueras](https://discuss.pomerium.com/u/sorin.flueras)\
**Post date:** [July 1, 2024, 6:36am UTC](https://discuss.pomerium.com/t/cross-origin-configuration/384/1 "2024-07-01T06:36:10Z")

</div>

There are three solutions provided at [Cross-Origin Configuration | Pomerium](https://www.pomerium.com/docs/guides/cors#problem) for fixing the 401 error related to cross-origin configuration. However, all three require changes to the application code. What can I do if I can’t modify the application code? Is there no alternative way to make it work across domains?

---

<div class="post-metadata">

**Author:** ![calebdoxsey](https://avatars.discourse-cdn.com/v4/letter/c/7bcc69/32.png) [@calebdoxsey](https://discuss.pomerium.com/u/calebdoxsey)\
**Post date:** [July 1, 2024, 5:17pm UTC](https://discuss.pomerium.com/t/cross-origin-configuration/384/2 "2024-07-01T17:17:02Z")

</div>

Hi @sorin.flueras ,

If you can’t change application code I think the only alternative would be to build something custom in front of the application code. In general, Pomerium does not provide features to do this.