admin管理员组

文章数量:1023803

I wonder what exactly the version nameing does?

like jquery.js?ver=1.4.4

I mean if I use a cdn like this jquery/1.4.4/jquery.min.js?ver=1.4.4 but another side has jquery/1.4.4/jquery.min.js?ver=1.3.2 in there, does this effect caching?

I wonder what exactly the version nameing does?

like jquery.js?ver=1.4.4

I mean if I use a cdn like this jquery/1.4.4/jquery.min.js?ver=1.4.4 but another side has jquery/1.4.4/jquery.min.js?ver=1.3.2 in there, does this effect caching?

Share Improve this question edited Jan 12, 2019 at 15:28 Cœur 38.8k25 gold badges206 silver badges279 bronze badges asked Dec 17, 2010 at 22:27 MrGlasspooleMrGlasspoole 4452 gold badges4 silver badges15 bronze badges
Add a ment  | 

1 Answer 1

Reset to default 8

Yes, by changing the =1.4.4 to something else, it forces the file to not be cached by the browser when a user es back to the page. So if you upgraded to a new version of JQuery say 1.4.5, and you wanted to make sure that the client got the most current version of the file, you change the end of the url. This makes the browser think that it's a brand new file and forces it to download the new version.

(Having the version at the end helps you easily identify which version of the file you have, but that is totally aside from what is being asked :) ).

I wonder what exactly the version nameing does?

like jquery.js?ver=1.4.4

I mean if I use a cdn like this jquery/1.4.4/jquery.min.js?ver=1.4.4 but another side has jquery/1.4.4/jquery.min.js?ver=1.3.2 in there, does this effect caching?

I wonder what exactly the version nameing does?

like jquery.js?ver=1.4.4

I mean if I use a cdn like this jquery/1.4.4/jquery.min.js?ver=1.4.4 but another side has jquery/1.4.4/jquery.min.js?ver=1.3.2 in there, does this effect caching?

Share Improve this question edited Jan 12, 2019 at 15:28 Cœur 38.8k25 gold badges206 silver badges279 bronze badges asked Dec 17, 2010 at 22:27 MrGlasspooleMrGlasspoole 4452 gold badges4 silver badges15 bronze badges
Add a ment  | 

1 Answer 1

Reset to default 8

Yes, by changing the =1.4.4 to something else, it forces the file to not be cached by the browser when a user es back to the page. So if you upgraded to a new version of JQuery say 1.4.5, and you wanted to make sure that the client got the most current version of the file, you change the end of the url. This makes the browser think that it's a brand new file and forces it to download the new version.

(Having the version at the end helps you easily identify which version of the file you have, but that is totally aside from what is being asked :) ).

本文标签: javascriptver at the end of includeis there a technical effectStack Overflow