[wp-trac] [WordPress Trac] #29201: File versioning should not use query strings, but rename the filename to allow caching

[WordPress Trac]

#29201: File versioning should not use query strings, but rename the filename to
allow caching
---------------------------+--------------------------
 Reporter:  benoitchantre  |       Owner:
     Type:  enhancement    |      Status:  closed
 Priority:  normal         |   Milestone:
Component:  Script Loader  |     Version:  3.9.1
 Severity:  normal         |  Resolution:  wontfix
 Keywords:                 |     Focuses:  performance
---------------------------+--------------------------

Comment (by drzraf):

 > A filename change would also solve that problem, but comes with it's own
 issues
 I'm in favor of removing completely these suffixing strategies.


 > Discussion can continue while the ticket is closed
 good to know

 > The versioning is used for cache-busting in events where browsers do not
 recheck the server version on a regular basis (for example, because it was
 served with a 30 day expiry).

 * Which browsers are affected?
 * What/Who may configure *by mistake* WP to set a too-large expire time?
 * ... and why would WP need to workaround these cases?
 * When a misconfiguration makes/made cache-busting mandatory, was it a bug
 from core, from a plugin, a specific situation (WP wp-admin/ files
 upgrade?), or from a misconfigured intermediary proxy? In the later case,
 is it still a software version in use nowadays?

 As an hypothetical example about supporting buggy
 softwares/misconfigurations, in the event Firefox would not send correctly
 If-Modified-Since, would it WP responsibility to use a standard-borderline
 URL-scheme as workaround, at the risk of affecting every other vendor?

--
Ticket URL: <https://core.trac.wordpress.org/ticket/29201#comment:8>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform