Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

#

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Jump to bottom

How to purge any Accept-Encoding cache ? #20

Closed
foxbin opened this issue Aug 9, 2018 · 2 comments
Closed

How to purge any Accept-Encoding cache ? #20

foxbin opened this issue Aug 9, 2018 · 2 comments

Comments

@foxbin
Copy link

foxbin commented Aug 9, 2018 •
edited
Loading

find /data/proxy_cache/ -type f |wc -l
0

192.168.60.99 m.xx.com - - [10/Aug/2018:01:35:47 +0800] "GET /purge/ask/118060.html HTTP/1.1" 412 186 - "-" "python-requests/2.19.1" "-" "-""0.000" "-" ""
192.168.60.99 m.xx.com - - [10/Aug/2018:01:35:47 +0800] "GET /purge/ask/118060.html HTTP/1.1" 412 186 - "-" "python-requests/2.19.1" "-" "-""0.000" "-" "gzip"
192.168.60.99 m.xx.com - - [10/Aug/2018:01:35:47 +0800] "GET /ask/118060.html HTTP/1.1" 200 23294 - "-" "python-requests/2.19.1" "-" "-""0.001" "MISS" ""
192.168.60.99 m.xx.com - - [10/Aug/2018:01:35:47 +0800] "GET /ask/118060.html HTTP/1.1" 200 5863 - "-" "python-requests/2.19.1" "-" "-""0.001" "MISS" "gzip"

find /data/proxy_cache/ -type f |wc -l
2

192.168.60.99 m.xx.com - - [10/Aug/2018:01:36:55 +0800] "GET /purge/ask/118060.html HTTP/1.1" 200 241 - "-" "python-requests/2.19.1" "-" "-""0.000" "-" ""
192.168.60.99 m.xx.com - - [10/Aug/2018:01:36:55 +0800] "GET /purge/ask/118060.html HTTP/1.1" 412 186 - "-" "python-requests/2.19.1" "-" "-""0.000" "-" "gzip"

find /data/proxy_cache/ -type f |wc -l
1

Unable to clear cache Accept-Encoding: gzip
/proxy_cache/ad/47/720ed608237b61e85ceac7d253e447ad
@foxbin foxbin changed the title how to purge any Accept-Encoding cache ? How to purge any Accept-Encoding cache ? Aug 9, 2018
@denji
Copy link
Member

denji commented Aug 9, 2018 •
edited
Loading

Do you have the gzip_vary option on?

@foxbin
Copy link
Author

foxbin commented Aug 13, 2018

After repeated testing, it is indeed caused by this problem.
Already solved, thanks!

@foxbin foxbin closed this as completed Aug 13, 2018
# for free to join this conversation on GitHub. Already have an account? # to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@denji @foxbin