How can we improve the Microsoft Edge developer experience?

Edge caching could be improved in error cases

I'm a developer on Azure CDN. When testing out some scenarios on our side, we noticed a difference in behavior between how Chrome browser and Edge browser work for caching some bad responses. In our CDN, if we detect that the eTag on an 'If-None-Match' request header is for a 'malformed eTag' (one with no quotes), such as If-None-Match: 64988f77337209c5a7157a016c456d02, we return a 400 response.

On chrome, the workflow goes like this:
Download page, get 200, everything fine.
Refresh page, browser sends If-None-Match with bad eTag, we detect this and send 400 to browser. Chrome detects this issue, and next refresh it does not send the If-None-Match, and request succeeds.

On Edge browser though, workflow goes like this:
Download page, get 200, everything fine.
Refresh page, browser sends If-None-Match with bad eTag, we detect this and send 400 to browser. Edge browser does detect this is a bad request/response (it clearly prints out HTTP 400 error
It’s not you, it’s this link (it appears to be broken)), but on additional refreshes it continues to send the bad If-None-Match etag instead of trying fresh like chrome does.

14 votes
Vote
Sign in
Check!
(thinking…)
Reset
or sign in with
  • facebook
  • google
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Douglas Dlutz shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

    0 comments

    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      Signed in as (Sign out)
      Submitting...

      Feedback and Knowledge Base