I recently made an observation when performing some tests on page loading.
Even though HMWP masks the paths and other assets, when you view the browser dev console > Network tab, when loading a page, the Request URL shows the entire WP path, plugin folder and filename that’s being loaded – which essentially circumvents what HMWP is supposed to do?
Please see screenshot of an example which shows the revslider file path.
Hi, thanks for contacting us. Regarding this (https://support.wpwave.com/wp-content/uploads/2020/06/Screen-Shot.png), this image might have been hardcoded somewhere or being referenced from some plugin’s/theme’s stylesheet. HMWP cannot rename such paths and you’ll need to manually replace those paths.
Also, HMWP makes use of re-write rules to rename/mask the default WP paths and does not physically rename any file or folder. Hence, the default WP paths will still be valid if accessed directly.
So in short, HMWP isn’t compatible with HTTP/2 push, period.
Please research the mechanics of h2 and how it works, plugins that help enable h2 asset push will always use the full path of the asset and not take into account the rewrite rules that HMWP adds to htaccess.
This is a problem because HMWP is then rendered useless.
Ok so it appears as though this happens if you use a plugin such as LScache which has the ability to HTTP/2 server push CSS and JS assets.
It uses the full path of the asset instead of it honouring HMWP.
>> Basically, these should or can also be changed to the new path (renamed by HMWP). Please, let us know where we can check this in your site so that we can look into it further.