Forum Replies Created
I’ve managed to resolve this issue after some further tweaking and disabling of a particular plugin (LSCache). Wappalyzer no longer detects WP as a result which is great.
Thanks for your great support as always 🙂
Gotcha, that makes sense.
Appreciate the update.
Brilliant, thanks Suman.
Thanks for your reply. So regarding your second point, definitely not a cached instance of wappalyzer as it’s been the case for a few weeks now, even before the LScache optimisations were added.
You might have to research any algorithm changes that they may applied recently to see if HMWP needs tightening up to support proper hiding.
I replied privately but can’t see the reply, let me know if you’ve received it.
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.
Any updates here please?
This is problem when using HTTP2 server push features with any plugin. It always uses the original file path vs HMWP’s rewrite rules.