When server responses 303, IE still keeps the original method in the next connection rather than using GET

Won’t fix Issue #904702


Oct 1, 2014
This issue is public.
Reported by 2 people

Sign in to watch or report this issue.

Steps to reproduce


Repro Steps:

  1. Use IE to open http://jigsaw.w3.org/HTTP/300/Overview.html
  2. Open F12 -> Network -> Start capturing
  3. Click 303 See Other button
  4. See your capture summary

Expected Results:

The second connection should use GET method.

Actual Results:

Dev Channel specific:



0 attachments

    Comments and activity

    • Microsoft Edge Team

      Changed Assigned To to “Tony S.”

      Changed Assigned To to “Khawar Z.”

      Changed Assigned To from “Khawar Z.” to “Ivan P.”

      Changed Assigned To from “Ivan P.” to “Ben K.”

      Changed Assigned To from “Ben K.” to “Manodasan W.”

      Changed Status to “Confirmed”

      Changed Assigned To from “Manodasan W.” to “IE F.”

      Changed Status from “Confirmed” to “Won’t fix”

    • https://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10.3.4

      Could this be fixed please… seems to break the spec.

      The response to the request can be found under a different URI and SHOULD be retrieved using a *GET* method on that resource
    • Will this be fixed? If not, why? If the Edge is the modern browser made by Microsoft, shouldn’ t it be compliant with rfc standart?

    • The issue is marked as 'Won’t fix’. But considering this violates the spec for 303, shouldn’t Edge be compliant with standards. We have a site which is broken only on Edge 14 and have to look for custom workarounds, which I thought is exactly what MS was intending to move away from with Edge. And so we are back to ‘IE specific blocks of code’ which is a bit naff. Would appreciate if you could look at fixing this at least in some future version.

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

    Sign in