Re^4: Using a git filter to Cache HTML Resources Locally

The interesting part is not the URL rewriting but the automatic download of the remote URL to a local file.

It wouldn't be hard to try to load both URLs from Javascript, or whatever, but why add additional complexity when you can just rewrite the file?

Comment on Re^4: Using a git filter to Cache HTML Resources Locally

Replies are listed 'Best First'.
Re^5: Using a git filter to Cache HTML Resources Locally by soonix (Chancellor) on Oct 12, 2018 at 08:53 UTC
This remarks reminds me of a caching proxy I had in use when internet connection time was metered in seconds. It might be possible to configure it to the same effect. For shielding your "work in progress" from local resources (CSS/JS/...) that are WIP themselves, however, the git filter can do what the proxy definitely can't.	[reply]
Re^5: Using a git filter to Cache HTML Resources Locally by Anonymous Monk on Oct 14, 2018 at 07:03 UTC
The interesting part is not the URL rewriting but the automatic download of the remote URL to a local file. Heh Downloading/mirroring is the boring part :)(lwp-rget/wget/curl/httrack...) The URL rewriting is the eyebrow raising part (sourcefilter) It wouldn't be hard to try to load both URLs from Javascript, or whatever, but why add additional complexity when you can just rewrite the file? Um, ... Why is one additional complexity but not the other?	[reply]
Re^6: Using a git filter to Cache HTML Resources Locally by haukex (Archbishop) on Oct 14, 2018 at 07:22 UTC
Why is one additional complexity but not the other? Rewriting the HTML is optional and local, while using JavaScript is global.	[reply]