301 redirect with gzip encoding fails to redirect properly

Fixed Issue #14859923

Details

Author
ADTC R.
Created
Nov 28, 2017
Privacy
This issue is public.
Found in
  • Microsoft Edge
Found in build #
38.14393
Reports
Reported by 1 person

Sign in to watch or report this issue.

Steps to reproduce

301 redirect with gzip encoding fails to redirect properly. The tab loading indicator keeps spinning and there’s no redirect happening.

The servers are very similar (same application), except one responds with gzip while the other doesn’t. The failing response fails only in Edge while it works in other browsers like Firefox.

Failing response (does not redirect, tab ‘loading’ indicator keeps spinning):

   Request URL: http://legacy-qa-2.us-east-1.elasticbeanstalk.com/
   Request Method: GET
   Status Code: 301 / Moved Permanently
 - Request Headers
   Accept: text/html, application/xhtml+xml, image/jxr, */*
   Accept-Encoding: gzip, deflate
   Accept-Language: en-US, en; q=0.5
   Connection: Keep-Alive
   DNT: 1
   Host: legacy-qa-2.us-east-1.elasticbeanstalk.com
   User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/51.0.2704.79 Safari/537.36 Edge/14.14393
 - Response Headers
   Connection: keep-alive
   Content-Encoding: gzip
   Content-Length: 215
   Content-Type: text/html; charset=iso-8859-1
   Date: Tue, 28 Nov 2017 20:00:30 GMT
   Location: https://legacy-qa-2.us-east-1.elasticbeanstalk.com/
   Server: Apache/2.2.34 (Amazon)
   Vary: Accept-Encoding

Working response (redirects properly):

   Request URL: http://legacy-qa.us-east-1.elasticbeanstalk.com/
   Request Method: GET
   Status Code: 301 / Moved Permanently
 - Request Headers
   Accept: text/html, application/xhtml+xml, image/jxr, */*
   Accept-Encoding: gzip, deflate
   Accept-Language: en-US, en; q=0.5
   Cache-Control: no-cache
   Connection: Keep-Alive
   DNT: 1
   Host: legacy-qa.us-east-1.elasticbeanstalk.com
   User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/51.0.2704.79 Safari/537.36 Edge/14.14393
 - Response Headers
   Connection: keep-alive
   Content-Length: 333
   Content-Type: text/html; charset=iso-8859-1
   Date: Tue, 28 Nov 2017 20:03:36 GMT
   Location: https://legacy-qa.us-east-1.elasticbeanstalk.com/
   Server: Apache/2.2.29 (Amazon)

Attachments

0 attachments

    Comments and activity

    • Btw, I’m not able to check and submit these options:

      The bug tracker website fails to save them. (using Firefox Quantum)

    • Microsoft Edge Team

      Changed Assigned To to “James M.”

    • Hello,

      Thank you for providing this information about the issue. We are pleased to report this feature is fixed in Edge and available in Insider Preview build 17046.

      Best Wishes,
      The MS Edge Team

    • Awesome! I’m glad to know that. What is the build number which fixes this, and when will it be released in the stable release channel (aka the regular-folks channel)?

    • Hello,

      I confirmed this is fixed in Edge 17. We are currently pushing out Edge 16 to all users accepting automatic updates, so I expect 17 will start being pushed out in the spring of 2018.

      Best Wishes,
      The MS Edge Team

    • Microsoft Edge Team

      Changed Status to “Fixed”

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

    Sign in