[wp-trac] [WordPress Trac] #58433: Improve Etag-based cache busting for styles and scripts (was: WP version in Etag header in load-styles.php file)

WordPress Trac noreply at wordpress.org
Wed Apr 3 17:54:27 UTC 2024


#58433: Improve Etag-based cache busting for styles and scripts
-------------------------------------------------+-------------------------
 Reporter:  dav4                                 |       Owner:  (none)
     Type:  enhancement                          |      Status:  new
 Priority:  normal                               |   Milestone:  Awaiting
                                                 |  Review
Component:  General                              |     Version:
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch needs-testing has-         |     Focuses:
  testing-info has-screenshots                   |
-------------------------------------------------+-------------------------
Description changed by ironprogrammer:

Old description:

> Hi
>
> I know there are plenty of plugins to hide WP version. You also decided
> to hide WP version from readme.html some time ago. When the user uses all
> possible methods to hide WP version, current version still can be checked
> by load-styles.php and load-scripts.php files. It is visible in eTag
> header.
>
> I know, this is not a big issue but I think is worth considering to use
> here some hash or checksum.
>

> Regards
> Dawid

New description:

 Improve how Etag headers are generated for styles and scripts to reflect
 changes in underlying script versions, rather than relying only on the WP
 version. This would address unexpected caching (`HTTP 304` responses)
 encountered during development in instances where a script's version has
 changed but the WP version has not.

 See comment:2.

 ''Updated to match direction this ticket has taken. Original description
 follows:''

 -----

 Hi

 I know there are plenty of plugins to hide WP version. You also decided to
 hide WP version from readme.html some time ago. When the user uses all
 possible methods to hide WP version, current version still can be checked
 by load-styles.php and load-scripts.php files. It is visible in eTag
 header.

 I know, this is not a big issue but I think is worth considering to use
 here some hash or checksum.


 Regards
 Dawid

--

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


More information about the wp-trac mailing list