Does not cope with UTF Location headers

Fixed Issue #8477507

Details

Author
Vladislav K.
Created
Aug 12, 2016
Privacy
This issue is public.
Found in
  • Microsoft Edge
Found in build #
14.14393
Reports
Reported by 1 person

Sign in to watch or report this issue.

Steps to reproduce

When this header is sent:
Location: http://business.medal.ladger.domain/marketing/всички-събития/

The url that this gets is:
http://business.medal.ladger.domain/marketing/всички-събития/

Then the url is typed into the browser it works.

I think this started to occur after the last update, but I cannot be sure. Chrome and Mozilla don’t do this.

Attachments

0 attachments

    Comments and activity

    • I know that standards state that Location header should be url encoded, but Chrome, Mozilla, AND Internet Explorer (surprise) read the header okay. Moreover after redirecting, in the address bar the location stays URL encoded instead of showing Cyrillic text.

      The typed URL stays in Cyrillic.

      Don’t get me wrong, I am a big fan of IE and Edge, but this is annoying.

    • Microsoft Edge Team

      Changed Assigned To to “Ibrahim O.”

    • Thank you for your feedback. Could you please provide us a repro link or attach a minimized sample or your code that produces this issue. This will help our investigation.

      All the best,
      The MS edge Team 

    • Hey, sorry for the delay, was on vacation.

      Here is the link: http://impero-ladger2.ladger.com/test/
      It is super simple - it just sends a single header "Location: страница1". It doesn’t work for me.

      If you however open it manually: http://impero-ladger2.ladger.com/test/страница1/, it will work.
      It you url encode it beforehand it will work, but my point is that the other browsers deal with that better.

    • Microsoft Edge Team

      Changed Status to “Fixed”

    • Appreciate the update. It appears to be this issue has been fixed and available in Windows Insider Preview version which also will be available in public stable soon. Since the issue is no longer reproducible I will go ahead and close this bug as fixed, please keep us posted if you see any inconsistency about this issue. Thanks again for your assistance in the investigation.

      All the best,
      The MS Edge Team

    • Can you post the version of the build so I can check when it comes out?

    • I have tested on Insider Preview 14905.

      Thanks,
      The MS Edge Team

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

    Sign in