code.jquery.com lacks IPv6 support

[mgol]

Originally reported by @tambry in jquery/jquery.com#178.

The jQuery CDN code.jquery.com lacks IPv6 addresses and thus resources from it can't be received using IPv6.

The CDN seems to be served by StackPath (previously Highwinds), which has recently gotten IPv6 support, so this should be fixable. For reference, BootstrapCDN also uses StackPath, and they recently enabled IPv6 for their CDN endpoint (stackpath.bootstrapcdn.com).

PS
Apologies if this is the wrong place to report this, but there doesn't seem to be any place to report issues related to code.jquery.com.

[zajdee]

BootstrapCDN has just enabled IPv6. Is it time for jQuery to follow suit now?

[zajdee]

I'm really curious on how to contact someone responsible for configuring the CDN for jQuery.
There's plain silence on the #jquery-infrastructure IRC channel (and it's like that for months, according to the logs).

Based on the last jQuery core meeting minutes, @mgol, @timmywil and @gibson042 have attended a core team meeting. Guys, sorry to bother you, but could you perhaps contact the infrastructure guys and ask them to follow up on this?

Thank you.

[mgol]

@zajdee I forwarded a question to StackPath. Note, though, that we have serious infrastructure team shortages & our setup is a bit rusty so it's not easy to make configuration changes until we sort it out.

[zajdee]

@mgol thank you so much. Is there perhaps something I could do to help the infrastructure team while the team is on shortage? Is there an option of volunteering or any other form of cooperation?

[kborchers]

I have been in touch with StackPath support and they are enabling IPv6 support. They did not provide an ETA but it should be very soon if not already enabled.

[mgol]

@zajdee The problem with the infrastructure team is that by definition it needs access to privileged services and we can't give such access to every person that would like to help. That said, we're in talks with the OpenJS Foundation so that our infrastructure needs get addressed; hopefully it'll get better over time. You can follow openjs-foundation/cross-project-council#285 for updates on that topic; perhaps involved in that issue may better know how to onboard new people to work on infrastructure.

[mgol]

The service should be available via IPv6 now. Please post a comment if that's not the case!

[yh1224]

I tried to access to code.jquery.com by IPv6, but received 403 ERROR!
I can't see some sites now.

[ec2-user@ip-172-31-21-126 ~]$ curl -6 https://code.jquery.com/jquery-3.4.1.min.js -w '%{http_code}\n' -o jquery.min.js
403
[ec2-user@ip-172-31-21-126 ~]$ curl -4 https://code.jquery.com/jquery-3.4.1.min.js -w '%{http_code}\n' -o jquery.min.js
200

[kylev]

From Xfinity in CA, I cannot reproduce @yh1224's result. IPv6 jQuery is working fine in-browser, too.

$ curl -6 https://code.jquery.com/jquery-3.4.1.min.js -w '%{http_code}\n' -o jquery.min.js
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100 88145  100 88145    0     0   753k      0 --:--:-- --:--:-- --:--:--  748k
200
$ curl -4 https://code.jquery.com/jquery-3.4.1.min.js -w '%{http_code}\n' -o jquery.min.js
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100 88145  100 88145    0     0   845k      0 --:--:-- --:--:-- --:--:--  852k
200

[yh1224]

It works from us-east-1 and us-west-2(AWS).

It fails from Japan(ap-northeast-1).
My address was 2406:da14:331:5601:5200:fd19:e0bd:213c.

[zajdee]

@yh1224 could you please also provide a tcptraceroute6 code.jquery.com 443 towards code.jquery.com?
I have just tested retrieving the file from Europe (CZ), South Africa (ZA, via Hurricane Electric) and Kenya (KE) and there is no issue there. So it might just be a Stackpath CDN misconfiguration in the APAC region.

[yh1224]

@zajdee Here's result.

ubuntu@ip-172-31-25-70:~$ tcptraceroute6 code.jquery.com 443
traceroute to cds.s5x3j6q5.hwcdn.net (2001:4de0:ac18::1:a:3a) from 2406:da14:331:5601:6c4a:4214:cfc1:86b4, port 443, from port 63179, 30 hops max, 60 bytes packets
 1  * * *
 2  * * *
 3  * * *
 4  * * *
 5  * * *
 6  2400:6500:0:4107:8000:0:6441:b01 (2400:6500:0:4107:8000:0:6441:b01)  33.099 ms  0.371 ms  0.344 ms
 7  2400:6500:0:1::3f (2400:6500:0:1::3f)  0.705 ms  1.370 ms  0.754 ms
 8  * * *
 9  2400:6500:0:1::3b (2400:6500:0:1::3b)  2.772 ms  2.716 ms  2.783 ms
10  * * *
11  * * *
12  2400:6500:0:1::62 (2400:6500:0:1::62)  2.704 ms  2.700 ms  3.768 ms
13  * * *
14  2400:6500:0:1::5d (2400:6500:0:1::5d)  2.837 ms  2.840 ms  2.815 ms
15  2001:de8:c::3:3438:1 (2001:de8:c::3:3438:1)  3.048 ms  3.038 ms  2.981 ms
16  2001:4de0:6310::11 (2001:4de0:6310::11)  2.951 ms  2.960 ms  2.948 ms
17  2001:4de0:ac18::1:a:3a (2001:4de0:ac18::1:a:3a)  2.854 ms [open]  * 2.662 ms [open]
ubuntu@ip-172-31-25-70:~$ tcptraceroute6 code.jquery.com 443
traceroute to cds.s5x3j6q5.hwcdn.net (2001:4de0:ac18::1:a:3b) from 2406:da14:331:5601:6c4a:4214:cfc1:86b4, port 443, from port 63174, 30 hops max, 60 bytes packets
 1  * * *
 2  * * *
 3  * * *
 4  * * *
 5  * * *
 6  2400:6500:0:4107:8000:0:6441:801 (2400:6500:0:4107:8000:0:6441:801)  0.554 ms  0.413 ms  3.193 ms
 7  2400:6500:0:1::8 (2400:6500:0:1::8)  4.142 ms  2.984 ms  3.019 ms
 8  * * *
 9  2400:6500:0:1::6 (2400:6500:0:1::6)  4.186 ms  6.318 ms  4.023 ms
10  * * *
11  * * *
12  2400:6500:0:1::62 (2400:6500:0:1::62)  4.000 ms  3.954 ms  3.958 ms
13  * * *
14  2400:6500:0:1::5d (2400:6500:0:1::5d)  4.014 ms  4.164 ms  4.921 ms
15  2001:de8:c::3:3438:2 (2001:de8:c::3:3438:2)  4.341 ms  4.393 ms  4.274 ms
16  2001:4de0:6310::12 (2001:4de0:6310::12)  4.034 ms  * 3.910 ms
17  2001:4de0:ac18::1:a:3b (2001:4de0:ac18::1:a:3b)  4.399 ms [open]  * *

[tambry]

@yh1224 What's the output of curl -6 https://code.jquery.com/jquery-3.4.1.min.js -I?

Does fetching files from the BootstrapCDN, which uses the same CDN and infrastructure have the same problem?