<FromGitter>
<drujensen> @samholst do you mind opening a ticket about this issue? If the origin header doesn’t exist, the CORS pipe should ignore it and not validate against the allowed list.
<FromGitter>
<drujensen> This would explain why other frameworks do not require it. ;-)
<FromGitter>
<eliasjpr> The browser should be setting the origin header it looks like is not doing that for case above which is why is requiring manually setting it up.
<FromGitter>
<eliasjpr> As per the 403 forbidden it is true that is should not be validated when the origin header is not present.
<FromGitter>
<eliasjpr> I recommend to having a separate pipeline when possible for CORS requests
<FromGitter>
<eliasjpr> For Firefox note: The Origin header is not set on Fetch requests with a method of HEAD or GET (this behavior was corrected in Firefox 65 — see bug 1508661).