Skip to content

Setting a host name interferes with CORS #1817

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
upi----- opened this issue Apr 7, 2025 · 0 comments
Open

Setting a host name interferes with CORS #1817

upi----- opened this issue Apr 7, 2025 · 0 comments
Labels
investigating Being checked

Comments

@upi-----
Copy link

upi----- commented Apr 7, 2025

Describe the bug
I'm using the latest docker version of OME.
I use ovenlivekit to stream WHIP to the server from a webpage.

I found that CORS only works correctly if Server.xml -> VirtualHosts -> VirtualHost -> Host ->Names -> Name is set to *. Setting it to an actual host name breaks CORS in the following way:

  • The initial preflight (OPTIONS) request to the WHIP URL is working correctly and returns the expected CORS headers.
  • The subsequent POST request to the WHIP URL is lacking all the CORS headers except "allowed headers", which causes CORS to fail.

To Reproduce
Steps to reproduce the behavior:

  1. Set Server.xml as follows:

    <Host>
        <Names>
            <Name>live.mydomain.com</Name>
        </Names>
     </Host>

CORS will no longer work.

Changing it back to the default:

<Host>
    <Names>
        <Name>*</Name>
    </Names>
 </Host>

works correctly.

Server (please complete the following information):

  • OS: Debian 12
  • OvenMediaEngine Version: v0.18.1
  • Branch: (whatever airensoft/ovenmediaengine:latest is built from)

Player (please complete the following information):

  • Device: Desktop
  • OS: Ubuntu Linux 24.11
  • Browser: Firefox 137, Chrome 135
@getroot getroot added the investigating Being checked label Apr 18, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
investigating Being checked
Projects
None yet
Development

No branches or pull requests

2 participants