Azure Question posted in
The official documentation to get you started can be found here.

Origin header missing on API call outside of network using Azure

I was getting a CORS error. I reviewed the spec and sure enough, my requests outside the network were missing the "origin" header.enter image description here

And then in network you can see the origin header

enter image description here

So I need help troubleshooting why the header "Origin" is getting stripped by Azure

Tags:

2

Answers


  1. Chosen as BEST ANSWER
    0

    It ended up being radware, which is a bot manager type deal. If anyone ever runs into this, the key is to do an OPTIONS request from outside the network. I did that in POSTMAN and then the radware response page came up. You should normally see 404 with an OPTIONS request, since there's no endpoint specifically assigned to that method usually. Check that your firewall allows OPTIONS requests in this circumstance.


  2. 0

    The Origin header is set by the browser, so this is not something ‘Azure’ can strip.

    The header will not be set if the origin matches the URL you’re opening.

    Login or Signup to reply.
Please signup or login to give your own answer.

Back To Top
Search