Share via

Has IIS changed the way XMLHttpRequest work on Windows Server 2022 Standard?

Anonymous
2024-02-19T15:07:46+00:00

I got some sort of messages regarding the use of Cross-Site webapps and how they interact. We use a frame on which we use the API components over Port and somehow we currently send the port over XSRF token in a non secure way. The thing is that IIS answer the Client request with the Domain and the accessed port which in this case is dynamic, ironically it only happens when we use Dynamic ports (1500>).

Any thoughts?

Windows Server Performance and maintenance

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question. To protect privacy, user profiles for migrated questions are anonymized.

0 comments

2 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2024-02-20T01:52:11+00:00

    Hello

    Thank you for posting in Microsoft Community forum!

    Based on the description, I understand your question is related to IIS.

    Since there are no engineers dedicated to this topic in this forum, in order to be able to get a quick and effective handling of your issue, I recommend that you repost your question in Stack Overflow or Microsoft Q&A, they are designed for developers.

    Thank you for your understanding and support. If you have any question or concern, please feel free to let us know.

    Have a nice day!

    Best Regards,

    Wesley Li

    0 comments
  2. Anonymous
    2024-02-22T16:28:59+00:00

    Exactly, it happens at IIS level. From what I got doing my research. I found that there would be any missing Plugin related to CORS or URL rewrite. Will advocate to other forums as well.

    Thanks for the prompt reply.

    0 comments