[wp-trac] [WordPress Trac] #28722: Boost performance with ETag in load-scripts.php and load-styles.php

[WordPress Trac]

#28722: Boost performance with ETag in load-scripts.php and load-styles.php
------------------------------+------------------------------------------
 Reporter:  sergej.mueller    |       Owner:  swissspidy
     Type:  feature request   |      Status:  closed
 Priority:  normal            |   Milestone:  4.5
Component:  Script Loader     |     Version:  4.0
 Severity:  normal            |  Resolution:  fixed
 Keywords:  has-patch commit  |     Focuses:  administration, performance
------------------------------+------------------------------------------

Comment (by RedSand):

 Replying to [comment:29 jeremyfelt]:
 > Hi @RedSand, thanks for taking the time to share your thoughts.
 >
 > We've been using WordPress version numbers on scripts and styles for
 quite a while to break client side caching after an upgrade. If we didn't
 use WordPress version numbers, we'd have to use another number that could
 be automatically scanned. If we didn't use that, then the size or content
 of the script itself would be used for automatic scanning.
 >
 > A benefit of having cache breaking version numbers attached to scripts
 is that it helps guarantee immediate upgrades if there ever is a security
 issue. It's also an easy way for us to ~~scold~~ nudge people we know that
 are running old versions of WordPress. :)
 >
 > I'm going to re-close this ticket as fixed as it is completed against
 the 4.5 milestone, which is now in RC2. I'd suggest a new ticket to
 continue discussing this concern, especially if there are other approaches
 that can be used to break scripts. Similar discussions are worth searching
 for as well, see #4155.

 Hi Jeremy,

 You're very welcome. :)

 Yes, I'm aware of the usage and the reasons for it, as I've been a
 WordPress developer and plugin developer for a decade. :)

 I'll be happy to open a separate ticket to explore this further for the
 next releases. Yes, there are a number of ways to break the caching
 without having to even add query strings. In fact, the use of query
 strings appended to the scripts actually creates a new performance issue,
 because caching scripts speeds up the site. But I won't get into that here
 and now.

 My main point here was that it would be better for the Etags to use some
 other unique string that could be updated when the version is changed, as
 opposed to the version number.

 I will put together some data and solutions for a new ticket.

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