Opened 7 years ago

Last modified 14 months ago

#1348 new defect

proxy_cache_background_update has problem with slice module

Reported by: RocFang@… Owned by:
Priority: minor Milestone:
Component: other Version: 1.13.x
Keywords: Cc:
uname -a: Linux localhost.localdomain 2.6.32-573.el6.x86_64 #1 SMP Thu Jul 23 15:44:03 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
nginx -V: configure arguments: --with-debug --prefix=/home/fangpeng/project/nginx/local/nginx-1.13.3 --with-http_slice_module

Description

When slice is not enabled, and proxy_cache_background_update enabled, the variable of upstream_cache_status will getting back to "HIT" after the revalidation.

But when we both enable proxy_cache_background_update and slice, the variable of upstream_cache_status will always be "STALE", no matter whether revalidation happends.

Change History (3)

comment:1 by Roman Arutyunyan, 7 years ago

Thanks for reporting this.
This happens because the $slice_range variable only makes sense in the main slice request.
In a subrequest (including background cache update subrequest) it evaluates to an empty string.
So instead of a slice the entire file is updated in background each time.

in reply to:  1 comment:2 by RocFang@…, 7 years ago

Replying to arut:

Thanks for reporting this.
This happens because the $slice_range variable only makes sense in the main slice request.
In a subrequest (including background cache update subrequest) it evaluates to an empty string.
So instead of a slice the entire file is updated in background each time.

Thanks for you replay, arut.
so what's the future plan about this? fix it or let it be a wont fix?

Last edited 7 years ago by RocFang@… (previous) (diff)

comment:3 by maximk-1@…, 14 months ago

Hi!
Any updates/future plans to fix it?

Note: See TracTickets for help on using tickets.