in reply to Re^5: Using a git filter to Cache HTML Resources Locally
in thread Using a git filter to Cache HTML Resources Locally

Sorry, I don't understand what point you're making, and I've already replied on the topic of JS vs. a git filter (twice). Protocol-relative URLs appear to be widely discouraged now, and as I already said, don't seem to help in this case anyway. Could you maybe show some example code of what you mean?

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

Replies are listed 'Best First'.
Re^7: Using a git filter to Cache HTML Resources Locally
by hippo (Archbishop) on Oct 14, 2018 at 12:26 UTC
    Protocol-relative URLs appear to be widely discouraged now

    This is news to me. Who is discouraging their use and why?

        Thanks for these references.

        The rationale in the Wikipedia and Nick Craver docs refer essentially to their internal policies for their own sites and make a good deal of sense. It does not seem from my reading of them that either is advocating a universal policy beyond that.

        Conversely the other 2 articles do advocate a universal policy. However, I find their arguments simplistic and therefore unconvincing. That said, it is still good to know that such points of view exist.

Re^7: Using a git filter to Cache HTML Resources Locally
by Anonymous Monk on Oct 15, 2018 at 02:01 UTC

    Let me try an funnalogy, as I don't see code contributing to understanding when simple english isn't

    me: why not a lightswitch?

    you: what are you crazy, I've already installed electrician to rewire the house on demand

    enjoy