Slot machines can be easy to win but only if you know this.Claim Your Free 999 Pesos Bonus Today

tworak
(@tworak)

6 years, 4 months ago

Hi,

Across a number of servers we see an occasional issue. (hard to replicate as it only happens every so often.

When you have the browser gzip compression option enabled, sometimes when we view the website it starts to download a file download.gz which contains a file named download which is the HTML source of the page.

As i mentioned if i disable the gzip option its back to normal (without Gzip though) if i re-enable it and clear cache its all fine. and will be for some time – often months until someone reports it occurring again and we repeat the process.

When its occurring im still able to login via admin.

Any idea on what could be casuing this? we do have mod_deflate installed and apache 2.4

Viewing 15 replies - 1 through 15 (of 25 total)

1 2 →

bgdstr
(@bogdanstratulat)

6 years, 4 months ago

First of all thank you for bringing this to our attention> Frankly I saw this being reported once before. Our developers have been notified about this, but at this moment there isn’t a registered bug. Is there any chance that next time when it happens this (if it happens) you can go and delete all the *.gz files from wp-content/ cache. If this helps, please get back to us and we will try to figure out a workaround. Looking forward to your reply.

Kind regards!
Bogdan S.

Thread Starter tworak
(@tworak)

6 years, 4 months ago

I cant see any .gz files in /public_html/wp-content/cache/ directly.

I can see some Files in the minify dir like

6bffe.css_gzip
6bffe.css_gzip_meta

Thread Starter tworak
(@tworak)

6 years, 4 months ago

Happened again just now. I deleted a few folders in cache to no result then i deleted the page_enhanced a sub folder and was fixed FTP logs are the files that i think did the trick were

_index_ssl.html_gzip
_index_ssl.html

would love to see a fix

full FTP logs were

[00:20:17] [R] 257 “/public_html/wp-content/cache/page_enhanced/www.xxxxxx.com” is your current location
[00:20:17] [R] DELE _index_ssl.html_gzip
[00:20:17] [R] 250 Deleted _index_ssl.html_gzip
[00:20:17] [R] DELE _index_ssl.html
[00:20:17] [R] 250 Deleted _index_ssl.html
[00:20:17] [R] CWD /public_html/wp-content/cache/page_enhanced
[00:20:17] [R] 250 OK. Current directory is /public_html/wp-content/cache/page_enhanced
[00:20:17] [R] PWD
[00:20:17] [R] 257 “/public_html/wp-content/cache/page_enhanced” is your current location
[00:20:17] [R] RMD https://www.xxxxxx.com
[00:20:17] [R] 250 The directory was successfully removed

hemendraajmera
(@hemendraajmera-1)

6 years, 2 months ago

I am also facing same, issue when website browser it download in zip. after i have to deactivate the plugin to website work as normal.
after deactivating plugin my website speed going slow, and it impact on visitors.
can you please check help to fix the problem.

Thanks in advance.

bgdstr
(@bogdanstratulat)

6 years, 2 months ago

as a temporary solution you can purge cache and everything should work as expected. This issue has been reported internaly and our developers are working on fix.

baskie
(@baskie)

6 years, 2 months ago

We have the exact same issue:
– Clear cache
– Most pages work except for 1 page (after that we stop testing so there might be more)
– It is a different page every time
– Gzip is enabled (i have checked on the server)
– Disabling
– We use Plesk

Since most pages are working OK, it seems to be something random.
Also, no log is generated server side: the page is served but is not parsed by the browser.

Partial enable gzip
– Disabling gzip on the top of the Browser Cache page
– Enabling only gzip fo CSS & JS
This resulted in perfect pages the first time of loading.
If we then closed Chrome Incognito and opened a new session, the pages would not parse CSS and JS properly. Resulting in deformed pages and error like this:
Resource interpreted as Stylesheet but transferred with MIME type application/octet-stream: "https://REMOVED/wp-content/cache/minify/f13e3.css".
and
Uncaught SyntaxError: Invalid or unexpected token
Network tab in Chrome shows no errors.

Temp solution
For now, we have had to disable all gzip in W3 Total Cache. Then the situation is stable.

By the way: we ditched WP Super Cache a few days ago to try W3. With WP Super Cache, Gzip has not given us these issues before in the 2 years of use.

Thanks,
Bas
vpls
(@vpls)

6 years, 1 month ago
as a temporary solution you can purge cache and everything should work as expected. This issue has been reported internaly and our developers are working on fix.

Same problem is now happening to our website. We removed the .htaccess code W3TC added the first time in order to prevent it from serving download.gz when viewing the homepage. After a day, it rewrote to the .htaccess and caused the same problem.

We’ve had to disabled the plugin until we can verify an updated patch.
- This reply was modified 6 years, 1 month ago by vpls. Reason: Adding Author's previous reply
Plugin Contributor Marko Vasiljevic
(@vmarko)

6 years, 1 month ago

Hello @vpls,

Can you please share w3tc part of the .htaccess?
vpls
(@vpls)

6 years, 1 month ago
Hi @vmarko,

Absolutely. We believe the Page Cache could be causing part of the problem.
```
# BEGIN W3TC Page Cache core
<IfModule mod_rewrite.c>
    RewriteEngine On
    RewriteBase /
    RewriteCond %{HTTPS} =on
    RewriteRule .* - [E=W3TC_SSL:_ssl]
    RewriteCond %{SERVER_PORT} =443
    RewriteRule .* - [E=W3TC_SSL:_ssl]
    RewriteCond %{HTTP:X-Forwarded-Proto} =https [NC]
    RewriteRule .* - [E=W3TC_SSL:_ssl]
    RewriteCond %{HTTP:Accept-Encoding} gzip
    RewriteRule .* - [E=W3TC_ENC:_gzip]
    RewriteCond %{HTTP_COOKIE} w3tc_preview [NC]
    RewriteRule .* - [E=W3TC_PREVIEW:_preview]
    RewriteCond %{REQUEST_METHOD} !=POST
    RewriteCond %{QUERY_STRING} =""
    RewriteCond %{REQUEST_URI} \/$
    RewriteCond %{HTTP_COOKIE} !(comment_author|wp\-postpass|w3tc_logged_out|wordpress_logged_in|wptouch_switch_toggle) [NC]
    RewriteCond "%{DOCUMENT_ROOT}/wp-content/cache/page_enhanced/%{HTTP_HOST}/%{REQUEST_URI}/_index%{ENV:W3TC_SSL}%{ENV:W3TC_PREVIEW}.html%{ENV:W3TC_ENC}" -f
    RewriteRule .* "/wp-content/cache/page_enhanced/%{HTTP_HOST}/%{REQUEST_URI}/_index%{ENV:W3TC_SSL}%{ENV:W3TC_PREVIEW}.html%{ENV:W3TC_ENC}" [L]
    RewriteCond %{REQUEST_METHOD} !=POST
    RewriteCond %{QUERY_STRING} =""
    RewriteCond %{REQUEST_URI} \/$
    RewriteCond %{HTTP_COOKIE} !(comment_author|wp\-postpass|w3tc_logged_out|wordpress_logged_in|wptouch_switch_toggle) [NC]
    RewriteCond "%{DOCUMENT_ROOT}/wp-content/cache/page_enhanced/%{HTTP_HOST}/%{REQUEST_URI}/_index%{ENV:W3TC_SSL}%{ENV:W3TC_PREVIEW}.xml%{ENV:W3TC_ENC}" -f
    RewriteRule .* "/wp-content/cache/page_enhanced/%{HTTP_HOST}/%{REQUEST_URI}/_index%{ENV:W3TC_SSL}%{ENV:W3TC_PREVIEW}.xml%{ENV:W3TC_ENC}" [L]
</IfModule>
# END W3TC Page Cache core
```
You may view the complete W3TC .htaccess here.
Plugin Contributor Marko Vasiljevic
(@vmarko)

6 years, 1 month ago
Hello,

Problems like this may have something to do with AllowOverwrite in Apache.
Can you please check apache config for <Directory path/to/website> and see if you have something similar to this:
```
<Directory "c:/wamp64/vhosts/mysite">
    AllowOverride All
    Order Allow,Deny
    Allow from All
</Directory>
```
hemendraajmera
(@hemendraajmera-1)

6 years, 1 month ago

As per your suggestion, I have activated and purge cache, the website will work as normal before with plugin. now suddenly it will happen again and the website goes down, again I have to deactivate the plugin.
I hope we have identified the root cause and ensured that this would not happen again.
Please release the latest update with this fix, many of website facing the issue.

Thanks in advance.

bgdstr
(@bogdanstratulat)

6 years, 1 month ago

Thank you for your patience. I have replied on the ticket that you have opened and a solution has been provided. I hope this helps.

vpls
(@vpls)

6 years, 1 month ago

Hi @bgdstr,

Would you mind sharing the fix here as we’re still looking for a fix.

fpokoj
(@fpokoj)

6 years ago

What happend with this topic @bgdstr ?

liftingcortical
(@liftingcortical)

6 years ago

Seems like it no longer sends the Content-Type header properly:
HTTP/1.1 200 OK
Date: Thu, 08 Nov 2018 09:04:28 GMT
Server: Apache
Vary: Accept-Encoding,User-Agent
Last-Modified: Wed, 07 Nov 2018 11:54:28 GMT
Accept-Ranges: bytes
Content-Encoding: gzip
Strict-Transport-Security: max-age=31536000
Referrer-Policy: origin
Link: </wp-content/cache/minify/469a8.js>; rel=preload; as=script
Link: </wp-content/cache/minify/5a084.js>; rel=preload; as=script
Link: </wp-content/cache/minify/545b0.js>; rel=preload; as=script
Link: </wp-content/cache/minify/5d1ad.js>; rel=preload; as=script
Link: </wp-content/cache/minify/6aaea.js>; rel=preload; as=script
Link: </wp-content/cache/minify/99006.js>; rel=preload; as=script
Link: </wp-content/cache/minify/02155.js>; rel=preload; as=script
Link: </wp-content/cache/minify/6e269.js>; rel=preload; as=script
Link: </wp-content/cache/minify/3ee41.js>; rel=preload; as=script
Link: </wp-content/cache/minify/0b066.js>; rel=preload; as=script
Link: </wp-content/cache/minify/1ebad.js>; rel=preload; as=script
Link: </wp-content/cache/minify/0c65a.js>; rel=preload; as=script
Link: </wp-content/cache/minify/344a7.js>; rel=preload; as=script
Link: </wp-content/cache/minify/4e8c0.js>; rel=preload; as=script
Link: </wp-content/cache/minify/c8498.js>; rel=preload; as=script
Link: </wp-content/cache/minify/4fb56.js>; rel=preload; as=script
Link: </wp-content/cache/minify/6cca5.js>; rel=preload; as=script
Link: </wp-content/cache/minify/7766c.js>; rel=preload; as=script
Link: </wp-content/cache/minify/4dd78.js>; rel=preload; as=script
Link: </wp-content/cache/minify/5c1bc.js>; rel=preload; as=script
Link: </wp-content/cache/minify/0351e.js>; rel=preload; as=script
Link: </wp-content/cache/minify/3ec36.js>; rel=preload; as=script
Link: </wp-content/cache/minify/32d0a.js>; rel=preload; as=script
Link: </wp-content/cache/minify/5f0d1.js>; rel=preload; as=script
Link: </wp-content/cache/minify/31e22.js>; rel=preload; as=script
Link: </wp-content/cache/minify/59632.js>; rel=preload; as=script
Link: </wp-content/cache/minify/d6903.js>; rel=preload; as=script
Link: </wp-content/cache/minify/9a50d.js>; rel=preload; as=script
Link: </wp-content/cache/minify/b9b52.js>; rel=preload; as=script
Link: </wp-content/cache/minify/275d1.js>; rel=preload; as=script
Link: </wp-content/cache/minify/67b50.js>; rel=preload; as=script
Link: </wp-content/cache/minify/822e0.js>; rel=preload; as=script
Link: </wp-content/cache/minify/98589.js>; rel=preload; as=script
Link: </wp-content/cache/minify/1e264.css>; rel=preload; as=style
Content-Length: 12628
Keep-Alive: timeout=5, max=100
Connection: Keep-Alive

Versus a proper response after purging all caches (see last lines)
HTTP/1.1 200 OK
Date: Thu, 08 Nov 2018 09:21:24 GMT
Server: Apache
Vary: Accept-Encoding,User-Agent
Last-Modified: Thu, 08 Nov 2018 09:09:06 GMT
Accept-Ranges: bytes
Content-Length: 12582
Strict-Transport-Security: max-age=31536000
Referrer-Policy: origin
Link: </wp-content/cache/minify/469a8.js>; rel=preload; as=script
Link: </wp-content/cache/minify/5a084.js>; rel=preload; as=script
Link: </wp-content/cache/minify/545b0.js>; rel=preload; as=script
Link: </wp-content/cache/minify/5d1ad.js>; rel=preload; as=script
Link: </wp-content/cache/minify/6aaea.js>; rel=preload; as=script
Link: </wp-content/cache/minify/99006.js>; rel=preload; as=script
Link: </wp-content/cache/minify/02155.js>; rel=preload; as=script
Link: </wp-content/cache/minify/6e269.js>; rel=preload; as=script
Link: </wp-content/cache/minify/3ee41.js>; rel=preload; as=script
Link: </wp-content/cache/minify/0b066.js>; rel=preload; as=script
Link: </wp-content/cache/minify/1ebad.js>; rel=preload; as=script
Link: </wp-content/cache/minify/0c65a.js>; rel=preload; as=script
Link: </wp-content/cache/minify/344a7.js>; rel=preload; as=script
Link: </wp-content/cache/minify/4e8c0.js>; rel=preload; as=script
Link: </wp-content/cache/minify/c8498.js>; rel=preload; as=script
Link: </wp-content/cache/minify/4fb56.js>; rel=preload; as=script
Link: </wp-content/cache/minify/6cca5.js>; rel=preload; as=script
Link: </wp-content/cache/minify/7766c.js>; rel=preload; as=script
Link: </wp-content/cache/minify/4dd78.js>; rel=preload; as=script
Link: </wp-content/cache/minify/5c1bc.js>; rel=preload; as=script
Link: </wp-content/cache/minify/0351e.js>; rel=preload; as=script
Link: </wp-content/cache/minify/3ec36.js>; rel=preload; as=script
Link: </wp-content/cache/minify/32d0a.js>; rel=preload; as=script
Link: </wp-content/cache/minify/5f0d1.js>; rel=preload; as=script
Link: </wp-content/cache/minify/31e22.js>; rel=preload; as=script
Link: </wp-content/cache/minify/59632.js>; rel=preload; as=script
Link: </wp-content/cache/minify/d6903.js>; rel=preload; as=script
Link: </wp-content/cache/minify/9a50d.js>; rel=preload; as=script
Link: </wp-content/cache/minify/b9b52.js>; rel=preload; as=script
Link: </wp-content/cache/minify/275d1.js>; rel=preload; as=script
Link: </wp-content/cache/minify/67b50.js>; rel=preload; as=script
Link: </wp-content/cache/minify/822e0.js>; rel=preload; as=script
Link: </wp-content/cache/minify/98589.js>; rel=preload; as=script
Link: </wp-content/cache/minify/1e264.css>; rel=preload; as=style
Keep-Alive: timeout=5, max=100
Connection: Keep-Alive
Content-Type: text/html; charset=UTF-8
Content-Encoding: gzip

So, yes, purging caches fixed. I’m guessing temporarily.
Cheers!