diff options
| author | Thomas Steur <tsteur@users.noreply.github.com> | 2019-11-08 06:09:57 +0300 |
|---|---|---|
| committer | diosmosis <diosmosis@users.noreply.github.com> | 2019-11-08 06:09:57 +0300 |
| commit | a6e68de3aef8daa0978edabbf867e5a86bfc6dac (patch) | |
| tree | ebfe84db1d26f7197939f84a6fa649ac7d8a98e7 /plugins/CoreHome/Tracker | |
| parent | ee4c3087779d43cd52a4fd8f31ed9e61489b8e79 (diff) | |
Fix error core JS proxy couldn't be decoded when gzipped (#15056)
* Fix error core JS proxy couldn't be decoded when gzipped
refs https://github.com/matomo-org/wp-matomo/pull/40
This happens when eg WordPress might be triggering a notice before we do the "readfile" in which case the notice will be mixed with the gzipped content in the response and therefore the browser cannot read the gzipped JS/CSS. You can easily reproduce this by eg replacing the `ob_get_clean` with an `echo 'foobar';`
Something I don't quite understand yet is why it works when echoing something after the `_readfile`. In theory we would need to exit right away.
* apply review feedback
Diffstat (limited to 'plugins/CoreHome/Tracker')
0 files changed, 0 insertions, 0 deletions