Using localhost to make a POST to remote server using CORS always does GET 200

Not reproducible Issue #19767072


Kevin C.
Nov 29, 2018
This issue is public.
Found in
  • Microsoft Edge
Found in build #
Reported by 4 people

Sign in to watch or report this issue.

Steps to reproduce

During app development while testing in the Edge browser we are not able to perform POSTs to another server in our network. This seems to be a CORS issue since we are running from localhost POSTing to xxxxx.xxxxxxx.local.

Every request results in a GET Method, Result 200, received from cache. No appropriate CORS message. Additionally we allow CORS requests on the server and this is not a problem for other browsers including IE.

Please provide any assistance and this is causing issues for our frontend developers


0 attachments

    Comments and activity

    • Microsoft Edge Team

      Changed Assigned To to “Veerabhadra r.”

    • Hi Kevin, Thanks for reporting your feedback. Could you please provide more information such as any snippet code, Logs or related docs that will help us to investigate further and reproduce this issue.


      The MS Edge Team

    • I can confirm this behavior in version 42.17134.1.0 / 17.17134. Developing angular app, currently served locally in development mode. Using alfresco api for user management (auth to get ticket) on remote server within our local network. But response is allways empty 200 from cache. Alfresco is configured properly and app works in Chrome, Firefox, Opera, … and IE11. Yes, works in IE11. I have already modified alfresco module, to force Cache-Control and Pragma no-cache headers in request, and modified url to append timestamp, so there is no chance that this request should be loaded from cache. But it is still from cache - here is screenshot from edge (in slovak language) - and this bug is also mentioned here -

    • Stuck with the same issue. Edge converting POST to GET (cors request) while no issues on any other browser.

    • At this time I will close out this issue. If you are still able to reproduce this issue on Microsoft Edge 44.17763.1.0 Microsoft EdgeHTML 18.17763 then please provide the details we requested and I will resume investigating this issue.

      Best regards,​​​​​​
      The Microsoft Edge Team.

    • Microsoft Edge Team

      Changed Assigned To from “Veerabhadra r.” to “Zachariah L.”

      Changed Status to “Not reproducible”

    • Hello,

      We still get the issue on Edge 44.17763.1.0:

      The request is a POST and not a GET.

    You need to sign in to your Microsoft account to add a comment.

    Sign in