This project is read-only.

setting the useCDN option while bundling disables the version parameter

May 8, 2014 at 4:45 AM
When the useCDN flag is set no version is appended ala www.theurltocdn.com/myBundle?v=aewuihrflkasdfasiuyeroiquwy4387wqer.


There are situations where the cdn is aware of the version parameter i.. its a pull through cdn. so the version number is desirable to invalidate the cache.

Solution: add an extra parameter to enable and disable the version parameter.
May 27, 2014 at 10:40 PM
+1 for this feature.

Another feature to incorporate the cachebuster into the bundle name. Example www.theurltocdn.com/aewuihrflkasdfasiuyeroiquwy4387wqer/myBundle .
Since HTTP 1.1 specifies that query string should not be used with static resources. (see http://webmasters.stackexchange.com/questions/63119/why-doesnt-firefox-cache-my-javascript-file/)

@ZSAndrewLong, the workaround for this issue for now is http://stackoverflow.com/questions/23145039/asp-net-optimization-framework-js-and-css-minification-and-bundling-using-cdn
May 28, 2014 at 1:56 PM
Thanks for the response!

"Another feature to incorporate the cachebuster into the bundle name."

I will definitely have to look into that

"Since HTTP 1.1 specifies that query string should not be used with static resources."

That is interesting... does that mean that the default bundler breaks firefox as is? (since it uses a version string)
May 28, 2014 at 4:33 PM
"We note one exception to this rule: since some applications have traditionally used GETs and HEADs with query URLs (those containing a "?" in the rel_path part) to perform operations with significant side effects, caches MUST NOT treat responses to such URIs as fresh unless the server provides an explicit expiration time."

wouldn't this suggest that as long as an explicit expiration time is set that uri's with parameters are valid?