<html>
<head>
<title>
Test page for saving a page with a broken image.
</title>
</head>
<body>
Content verification marker:
broken-image.htm: 1e846775-b3ed-4d9c-a124-029554a1eb9d
<br>
<br>
The picture below is broken on purpose, to test additional code paths:
<br>
<img src="broken-image.png">
<img src="broken-image.png">
<br>
We have 2 identical img tags above, because this used to trigger a
DCHECK in MHTMLPartsGenerationDelegate::shouldSkipResource (the
DCHECK would think that an img with a broken tag is included twice
as an MHTML part; MHTML files that have 2 MHTML parts with the same
URI render fine in Chrome, but fail in Internet Explorer). See
https://crbug.com/586680 for some more details about the DCHECK.
OTOH, this test hopefully covers more than just testing this one
DCHECK - hopefully the broken image scenario hits some other corner
cases as well.
<br><br>
The link to the image below is broken on purpose, to test additional code
paths - in particular in this case ResourceHandler::OnResponseStarted
is not called at all and the failure is reported directly via
ResourceHandler::OnResponseCompleted. See also https://crbug.com/594219.
<img src="http://f0b310b1-4038-46a8-ac98-529187682f2d.no.such.host/x.png">
<br><br>
</body>
</html>