Skip to main content

Bug Tracker

Side navigation

#7065 closed enhancement (fixed)

Opened September 22, 2010 07:30PM UTC

Closed November 24, 2010 08:48PM UTC

Last modified March 13, 2012 10:19PM UTC

jquery.com referencing google CDN's 1.4 (e.g. latest version) instead of 1.4.2 (current version).

Reported by: musicisair Owned by:
Priority: high Milestone:
Component: web Version:
Keywords: jquery.com google cnd Cc:
Blocked by: Blocking:
Description

An article about using Google CDN's for hosting jQuery mentioned something unfortunate about jquery.com's particular use of the CDN itself.

Read the "Specificity is crucial" section of http://encosia.com/2010/09/15/6953-reasons-why-i-still-let-google-host-jquery-for-me/.

The max-age for "latest-version" versions on Google's CDN is 3600 seconds - that would be 1 minute. Specifying the version explicitly (1.4.2 instead of 1.4) means it would be cached for 31536000 seconds...which is one year (except, of course, on a leap year). While we do love jQuery very much...we don't really want to download it every time we want visit.

Please change "http://ajax.googleapis.com/ajax/libs/jquery/1.4/jquery.min.js" to "http://ajax.googleapis.com/ajax/libs/jquery/1.4.2/jquery.min.js".

I couldn't find anywhere to file a ticket for jQuery.com, so please forgive me if this is the wrong place.

Attachments (0)
Change History (4)

Changed September 22, 2010 09:32PM UTC by musicisair comment:1

Correction: The max-age for "latest-version" versions on Google's CDN is 3600 seconds - that would be 1 __hour__.

Changed October 13, 2010 02:30AM UTC by snover comment:2

component: unfiledweb
priority: → high
status: newopen

Changed November 24, 2010 08:43PM UTC by mikehostetler comment:3

I've updated jquery.com homepage to point at the correct version of jQuery, hosted on jQuery's CDN.

Changed November 24, 2010 08:48PM UTC by addyosmani comment:4

_comment0: Closing as the fix for this has now been verified as having been completed.1290632482882502
resolution: → fixed
status: openclosed

Closing as a fix for this has now been verified as having been completed. Note: We are still debating whether local CDN referencing vs. Google's CDN usage warrant a further update to the site. If we opt not to use local CDN, I will confirm that via this ticket for historical reference.