search

jquery / codeorigin.jquery.com

jQuery CDN
https://releases.jquery.com
Other
57 stars 602 forks source link

Purge not working as expected #45

Closed trentmwillis closed 5 years ago

trentmwillis commented 5 years ago

The QUnit git build hasn't updated in a while (since version 2.6.3-pre) which corresponds to when the CDN API changed and the purge endpoint was updated.

According to this Jenkins log, the file should have been updated successfully, but you can see here that the version is still out-of-date (should be version 2.8.1-pre).

cc @Krinkle

Krinkle commented 5 years ago

Meanwhile, I've also tried purging it from the Highwinds StrikTracker web interface ("Purge Content"), and while it shows a nice progress bar going from 1% to 100% and says "Content was successfully purged." at the end – it didn't seem to actually have any effect.

Krinkle commented 5 years ago

Yep, that's right. The WordPress server(s) we operate respond to codeorigin.jquery.com, which by default diverts any accidental traffic to the CDN (via code.jquery.com), but ?view bypasses that.

ElliotNB commented 5 years ago

@trentmwillis @Krinkle Any update on this issue? According to @arschmitz this issue is also holding up the release of jQuery Mobile 1.5.

Krinkle commented 5 years ago

Yeah, this is being looked into. There is a support ticket on-going with StackPath (Highwinds) for several weeks. Earlier this week on Tuesday, I finally got an answer about why this broke.

It appears something changed in their Purge API, specifically, if an origin web server varies its responds in some way (e.g. based on Accept-Encoding for gzip, or based on some other header) then purging the URL from the CDN no longer purges the variants (or indeed anything, it seems).

There is an undocumented API parameter in their API that is meant to fix this, which I'll try out momentarily.