Add option to download from cdn to local folder while cdn not supporting IPV6 [#2473863]

Hi,

For all people who implements IPV6 and use files via bootstrap CDN its impossible to have template working due the lack of support for IPV6 on CDN.

I already open a issue on github ( https://github.com/MaxCDN/bootstrap-cdn/issues/533 ) but there is no ETA to have IPV6 support.

It is being worked on, we do not have an ETA as of now. I will follow up once it is deployed.

I know I can use "method 1" alternative way to put files on my server but for the simplicity of less tech users a option to download from cdn and use files from disk is the better option.

It's also s good idea to put a waning on documentation about the lack of IPV6 support on cdn.

Comments

Comment #1

PedroMiguel CreditAttribution: PedroMiguel commented 18 April 2015 at 16:13

Issue summary:

View changes

Comment #2

markhalliwell

English

CreditAttribution: markhalliwell at Tag1 Consulting commented 22 April 2015 at 20:13

Status:

Active

» Closed (won't fix)

IPv6 is a browser/DNS/server issue, not anything this project can really tackle. The alternative method 1 (serving the files locally) is the only "solution" for this as we do not control MaxCDN's IPv6 capabilities.

Comment #3

PedroMiguel CreditAttribution: PedroMiguel commented 22 April 2015 at 20:41

Hi markcarver,

Thanks for your reply. Yes, I understand that, it's more a protocol issue and nothing maintainers can do about that beside warning users for that fact. (Ie: on project page or on the readme file).

Something like this: "If you are using IPV6 on your site you should not use the CDN option as currently MaxCDN's do not provide IPv6 capabilities."

Comment #4

markhalliwell

English

CreditAttribution: markhalliwell at Tag1 Consulting commented 22 April 2015 at 22:14

I'm not going to say that. Just because MaxCDN doesn't does not yet support that protocol, doesn't mean that the DNS address will not properly resolve to the existing IPv4 address. IPv6 isn't the norm and modern browsers should already have fallback support when there isn't a proper IPv4 DNS resolution. That is why IPv6 is being rolled out slowly/in phases, so IPv4 can eventually phased out properly, until it does... almost everything should resolve normally. Most people doesn't even see or know about this difference.

http://ipv6-test.com/
http://test-ipv6.com/simple_test.html
http://www.google.com/intl/en/ipv6/faq.html
http://www.google.com/intl/en/ipv6/statistics.html#tab=per-country-ipv6-...
http://serverfault.com/questions/421445/should-i-use-ipv6-only-or-both-i...

Comment #5

PedroMiguel CreditAttribution: PedroMiguel commented 22 April 2015 at 22:47

OK, You are the mantainer, you decide...

I just was open this request because I'm implementing IPv6 and this is a issue where I waste some hours of work when tests fail. So, as a developer/site builder (who are the target for drupal themes, not the main public) I'd like to see this info before having headhaches about thing not working. But that is myself :)

From now, at least is on the theme issue list and people could seach/find that.

Btw, Thanks for the sites, I already know that, but for IPv6 issues and questions you should use RIPE ( https://www.ripe.net/publications/ipv6-info-centre ) as this is the official organism for network admin. And just for curiosity, RIPE is being last month on a lot of meetings wordlwide with local providers to speedup IPv6 implementation. (but that is out of the scoop of this issue list).

Once again, thank for your time replying to this issue.

Comment #6

markhalliwell

English

CreditAttribution: markhalliwell at Tag1 Consulting commented 23 April 2015 at 17:20

You're welcome, but I just don't see how this is really an issue for this project (nor MaxCDN).

If you are using IPV6 on your site you should not use the CDN option as currently MaxCDN's do not provide IPv6 capabilities.

This statement is completely false.

Embedding the CDN version of bootstrap shouldn't "fail" as you suggest just because your site is IPv6. The embedded stylesheets and javascript that point to the domain for BootstrapCDN/MaxCDN should resolve normally and the browser should fallback to an IPv4 address when attempting to resolve itself if no IPv6 address is available.

This has nothing to do with this project nor really the server you're implementing IPv6 on. If anything, any "failure" would actually be in the browser you are using and its ability to provide proper fallback support to IPv4 when IPv6 isn't available (which Chrome has had since version 11 or something I think... not sure about the others).

FWIW, this project has moved on to using jsDelivr as the primary CDN (which is supplied by BootstrapCDN/MaxCDN): https://www.drupal.org/node/2452617

Comment #7

markhalliwell

English

CreditAttribution: markhalliwell at Tag1 Consulting commented 7 May 2015 at 19:40

@PedroMiguel, FWIW, I've actually just upgraded https://dreditor.org so it's IPv6 capable. The server itself is is capable of serving over IPv4 and IPv6 and works if the client (my browser) has an IPv4 or IPv6 connection.

That is also because I'm behind an ISP that provides both IPv4 and IPv6 addresses. If you were to visit the site from just an IPv6 connection, the CDN does indeed not work, but that is because the user (me) would be behind an IPv6 only network.

Such networks shouldn't really exist considering that IPv6 is not yet a fully adopted and realized protocol (regardless of how old it is, it's just a fact).

So any real "issue" is really your current network configuration, not really any CDN and certainly not this project.