.htaccess was not updated

Hello @peterkueger

Thank you for your inquiry and I am happy to assist you with this.
Can you please share the part of the .htaccess where you see this so we can check.
Thanks!

I’m sorry, but I don’t remember the exact content.

But it was a preloading of the minified scripts.

I believe, this problem, if you choose “automatic” in the “General settings” and choose “enabled” for “JS” in the “Minify settings” with a “HTTP2 preload”.

After this, call a page, so it’s generated in the enhanced page cache.

Then please disable “HTTP2 preload”. I believe, now you still have the preload code inside the .htaccess of the enhanced page cache.

Sorry, that I didn’t copy the content of that .htaccess file before. With other plugins, I learned developer of them are often not very interested to fix bugs. Up from now, I will document issues better for you.

Hello @peterkueger

Thank you for the information.
I’ve tried to replicate the issue by enabling HTTP/2 push and disable it and I am not seeing any issues.
Thanks!

I tried it again – and the problem still exists.

After this, I had the following file:
\wp-content\cache\page_enhanced\localhost\.htaccess

with this content:
<IfModule mod_headers.c>
<FilesMatch “\.html[_a-z]*$”>
Header unset Link
Header add Link ‘</wp-content/cache/minify/15cc3.js>; rel=preload; as=script’

Header add Link ‘</wp-content/cache/minify/8c21a.js>; rel=preload; as=script’

Header add Link ‘</wp-content/cache/minify/07eed.css>; rel=preload; as=style’

Header add Link ‘</wp-content/cache/minify/16913.css>; rel=preload; as=style’
</FilesMatch>
</IfModule>

So I don’t agree with you, that this problem is resolved. But if you are not able to reproduce this problem, maybe you are the wrong one to understand this bug?

I disabled the minifying first. After than, I disabled the HTTP2 proload.

Hello @peterkueger

Thank you for the information and clarification.
I was thinking about the main .htaccess file so thank you for pointing that out.
Yes, that is correct. Once HTTP/2 push is enabled those rules are created in \wp-content\cache\page_enhanced\localhost\.htaccess
And when inspecting the source of your website you can see the following in the screenshot(I am using Cloudflare)
However, once HTTP/2 push is disabled, the rules remain in the \wp-content\cache\page_enhanced\localhost\.htaccess but in this case, they do not apply because the option is disabled and you can see the effect in this screenshot.
This is why the mentioned .htaccess rules are in the \wp-content\cache\page_enhanced\localhost\.htacces and not in the .htaccess in the root of your website.
This being said I can confirm that those rules remain after disabling HTTP/2 push but have no effect if disabled. This is simply the best way to do it to avoid deleting the files but simply updating it if needed. You can also manually delete the mentioned file if you see fit.
I hope this helps!
Thank you!

Thank you for confirming the bug in you software. And I honor, that you confirm not to be able to fix it. It’s not easy to tell other people his own limitations.

But I don’t agree with you, that the remaining rules does not bother me. They will be transmitted to the browser – and initiate there a request to the related files.

This forces unneeded traffic and shows, that I’m not able to configure my system as well.

If I remember well, they are also not removed, if I press your button to clear the Minify cache.

But you do not need to assist me. I find solutions for my by myself. I just wanted to tell you bugs of your software, to support you to improve it. Now I learned, you are not interested to do this, so I will not write the other bugs I found.

In love.

Hello @peterkueger

Thank you for taking the time to post this issue.
I can see where the confusion is. You need to purge all cache, not just minify cache, since http2 is a property of the page.
So once you disable HTTP/2 push, save all settings and purge the cache.
I hope this helps!

Marko,

seems you have a lot of problems understanding me. I didn’t post here to get assistance from you. I tried to tell you a bug, you could fix to improve W3TC. But now I found out, you do not have any intention to fix bugs.

Because of this, there is no reason, why I should post further more.

In Love.