prefer https

[b3rnd]

No description provided.

[lewisje]

While you're at it, it might be better to prefer rawgit.com over raw.githubusercontent.com (to reduce bandwidth on GitHub's servers).

[b3rnd]

http://rawgit.com/faq - "Requests to cdn.rawgit.com are routed through MaxCDN's super fast content delivery network, and are cached permanently" - means no updated filter lists, right? not really what we want... ;)

[lewisje]

I guess you mean client-side, because I know that it gets updated on RawGit when I update a file on GitHub.

[chrisaljoudi]

@lewisje @b3rnd

RawGit provides two URLs:

The CDN URL is indeed cached permanently (tested here), but the other one (the non-CDN one) isn't cached permanently and will occasionally issue more requests to GitHub for updates.

Given those circumstances, it'd have to be either rawgit.com or raw.githubusercontent.com (not cdn.rawgit.com).

However, the only advantage to using rawgit.com is the Content-type headers being appropriate (plus a small amount of short-term caching). Other than that, it hits both rawgit.com and raw.githubusercontent.com (which is arguably worse than just hitting the latter).

So it seems like raw.githubusercontent.com is the only reasonable answer for lists hosted exclusively on GitHub.

[jvoisin]

Is there something to correct/fix/improve to get this pull-request merged?