Bug 951224
Summary: | [Regression] maximum_object_size is ignored | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Jan Kratochvil <jan.kratochvil> |
Component: | squid | Assignee: | Michal Luscon <mluscon> |
Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | medium | Docs Contact: | |
Priority: | unspecified | ||
Version: | 18 | CC: | chris, henrik, jan.kratochvil, jonathansteffan, mluscon, pdericson, thozza |
Target Milestone: | --- | Keywords: | Regression |
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
URL: | http://bugs.squid-cache.org/show_bug.cgi?id=3830 | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2014-02-05 20:35:47 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Jan Kratochvil
2013-04-11 17:18:00 UTC
Try this: cache_dir ufs /var/spool/squid 10000 16 256 max-size=10485760 maximum_object_size 10 MB X-Cache: HIT from host2.jankratochvil.net X-Cache-Lookup: HIT from host2.jankratochvil.net:3128 Wow, it works, thanks. So the bug is in that the last line is no longer valid for new Squid: # TAG: maximum_object_size (bytes) # The default limit on size of objects stored to disk. # This size is used for cache_dir where max-size is not set. Another problem is latest Fedora Squid NVR is terribly obsolete (Bug 909940). No problem, I found your bug and one other earlier in the day - I had the same issue with 3.3.4. Other bug: http://bugs.squid-cache.org/show_bug.cgi?id=3830 I might have stumbled on the cause of this today after realising my squid install wasn't caching objects > 4MB. maximum_object_size will be observed by cache_dir if it appears before the cache_dir line in the config file. squid.conf.documented unfortunately documents the two items as: # TAG: cache_dir [..] # TAG: maximum_object_size [..] so it would be easy for one to configure these 'out of order'. Hope that helps. This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '18'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior to Fedora 18's end of life. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed. |