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

Steps to reproduce the problem:
1. Browse to https://tools.ietf.org/html/rfc2557
2. Save as MHTML
3. Reopen the file in Chrome
4. Scroll down to "Table of Contents" and follow a link to any section
5. Observe that the browser will fetch the original page from the Internet and go to the chosen section.

What is the expected behavior?
The browser should go to the chosen section in the local MHTML file instead of fetching the remote source.

What went wrong?
Since the primary purpose of the MHTML format is for offline viewing, it makes no sense that links that refer to the same page should trigger fetching the page from the internet.

Did this work before? N/A 

Chrome version: 56.0.2924.76  Channel: stable
OS Version: 6.1 (Windows 7, Windows Server 2008 R2)
Flash Version: Shockwave Flash 24.0 r0

Looking at the generated MHTML, it seems that even relative links in the form of "#section-1" are serialized (both in Chrome and IE) to MHTML with the full path, i.e. "https://tools.ietf.org/html/rfc2557#section-1". When I edited the generated MHTML to change the links back to their original relative form, I noticed a difference in behavior between Chrome an IE. Chrome will _still_ fetch the page from the Internet, whereas IE will jump to the relevant section on the local MHTML page. Firefox with the "Mozilla Archive Format" extension, will both save to MHTML using the original relative url, and will jump to the local section even when opening a file saved with the full URL.