Tats Shibata
Forum Replies Created
Viewing 4 replies - 1 through 4 (of 4 total)
-
Forum: Plugins
In reply to: [WP Super Cache] [Plugin: WP Super Cache] Gzip bug?I reproduced it, too. The below is the log of curl:
$ curl -Ov http://rewse.jp/blog/index.php * About to connect() to rewse.jp port 80 * Trying 183.77.251.234... connected * Connected to rewse.jp (183.77.251.234) port 80 > GET /blog/index.php HTTP/1.1 > User-Agent: curl/7.15.5 (x86_64-redhat-linux-gnu) libcurl/7.15.5 OpenSSL/0.9.8b zlib/1.2.3 libidn/0.6.5 > Host: rewse.jp > Accept: */* > < HTTP/1.1 200 OK < Date: Sun, 27 May 2012 08:56:11 GMT < Server: Apache < X-Powered-By: PHP/5.3.3 < Vary: Accept-Encoding,Cookie,User-Agent < Cache-Control: max-age=3, must-revalidate < WP-Super-Cache: Served supercache file from PHP < Content-Encoding: gzip < Content-Length: 15309 < Last-Modified: Sun, 27 May 2012 08:54:16 GMT < X-FRAME-OPTIONS: DENY < Content-Type: text/html; charset=UTF-8 < Content-Language: ja % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 15309 100 15309 0 0 52338 0 --:--:-- --:--:-- --:--:-- 1997k $ file index.php index.php: gzip compressed data, from UnixEnv:
- WordPress 3.3.2 ja
- WP Super Cache 1.1
Thanks,
TatsI’ve just confirmed to fix that by the latest development version. Thanks a lot.
The development version doesn’t fix that. Some other settings might be different between you and me.
I put the below 2 lines just in front of the if statment (line 167 on wp-cache-phase1.php of the dev version).
wp_cache_debug("wp_cache_slash_check: $wp_cache_slash_check", 5); wp_cache_debug("wp_cache_request_uri: $wp_cache_request_uri", 5);The below was my result. May I have your these 2 values?
15:41:21 /blog/ wp_cache_slash_check: 0 15:41:21 /blog/ wp_cache_request_uri: /blog/Thank you for the analysis. WordPress always meddles in line break… I’m using Disable WPAUTOP plugin but the issue happens. I’ll look for the root cause.
Thanks,
Viewing 4 replies - 1 through 4 (of 4 total)