NB: using ' instead of ", and trying to escape properly
NB: tests results not updated yet
NB: '&' in an SVG text (still) not handled
Fixes#152Fixes#153
If a URL is resolved before checking for absolute URLs, even relative
URLs will be detected as absolute.
Includes updates to the skip-absolute-urls test.
Closes#126
If the page is using rel="shortcut icon" instead of rel="icon", the
author will be surprised that the icon was not inlined, and may not
notice. It would be better to inline that icon.
Includes updates to the favicon tests.
Related to issue #126
Fixes#104
It will warn about them, but not fail the job, instead replacing the URL with '' (which is just as bad as the corrupted url, but at least it finishes).
When doing a request with the node request module with an URL
containing UTF-8 chars, some webservers will fail to find the file.
Therefore encodeURI on the url before requesting it.
Not sure if this is the best way to test it, but it works with all test cases.
Example of page which doesn't inline properly:
http://hotpoticeland.com/holsgerdislaug/
which links to the image:
http://hotpoticeland.com/wp-content/uploads/Hólsgerðislaug-300x225.jpg
The issue here was that although the "simple" detection was in place if the URL looked like HTML (i.e. has an angle bracket in it), but it didn't ever set the `isFile` flag.
This fix corrects this, but also swallows ENOENT errors, to mirror >=400 response codes being swallowed (i.e. return an empty body).
Fixes#89
* feature/clean-progress-output:
style: lint fixes
feat: enhance and clean -v output
fix: job counts (was missing JS + inline styles)
feat: show status if output redirected
fix: don't try to encode SVG if there's no body
* 'feature/local-only' of https://github.com/eigenuser/inliner:
chore: renamed flag to --skip-absolute-urls
chore: renamed flag to --same-origin-only
feat: support for only inlining local files
