UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/71.0.3578.98 Safari/537.36

Steps to reproduce the problem:
1. Add a listener chrome.webRequest.onHeadersReceived.addListener for all URLs where you manipulate details.responseHeaders
2. Open a URL: "http://www.myntra.com" and observe that above listener is invoked.
3. The above URL is server redirected with HTTP status code 301 to "https://www.myntra.com". Although the second request is shown in network logs in Inspect window, but the request is not intercepted by extension this time.

What is the expected behavior?
Network Request should always be intercepted by the extension.

What went wrong?
301 redirected requests are not intercepted by chrome extension webRequest APIs.

Did this work before? N/A 

Does this work in other browsers? N/A

Chrome version: 71.0.3578.98  Channel: stable
OS Version: 10.0
Flash Version: