Bug 951224 - [Regression] maximum_object_size is ignored
Summary: [Regression] maximum_object_size is ignored
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: squid
Version: 18
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Michal Luscon
QA Contact: Fedora Extras Quality Assurance
URL: http://bugs.squid-cache.org/show_bug....
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-04-11 17:18 UTC by Jan Kratochvil
Modified: 2014-02-05 20:35 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-02-05 20:35:47 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Jan Kratochvil 2013-04-11 17:18:00 UTC
Description of problem:
My scripts started repeatably downloading huge files.
It was always immediate in F-16 as the files were cached.

squid caches files up to 4MB which is the default of 'maximum_object_size'.
One cannot override it for higher size.

Version-Release number of selected component (if applicable):
PASS: squid in F-16
Unknown in F-17.
FAIL: squid-3.2.9-1.fc18.x86_64

How reproducible:
Always.

Steps to Reproduce:
cat >>/etc/squid/squid.conf <<EOH
cache_dir ufs /var/spool/squid 10000 16 256
maximum_object_size 10 MB
EOH
systemctl restart squid.service
head -qc 5m /dev/zero >/var/www/html/test
http_proxy=http://127.0.0.1:3128 curl -v -H Pragma: -o test -R -S --fail http://localhost/test
http_proxy=http://127.0.0.1:3128 curl -v -H Pragma: -o test -R -S --fail http://localhost/test

Actual results:
X-Cache: MISS from host2.jankratochvil.net
X-Cache-Lookup: MISS from host2.jankratochvil.net:3128

Expected results:
X-Cache: HIT from host2.jankratochvil.net
X-Cache-Lookup: HIT from host2.jankratochvil.net:3128

Additional info:

Comment 1 Peter Ericson 2013-05-01 12:24:56 UTC
Try this:

cache_dir ufs /var/spool/squid 10000 16 256 max-size=10485760
maximum_object_size 10 MB

Comment 2 Jan Kratochvil 2013-05-01 12:36:15 UTC
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).

Comment 3 Peter Ericson 2013-05-01 12:53:12 UTC
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

Comment 4 Chris Bennett 2013-05-20 07:25:17 UTC
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.

Comment 5 Fedora End Of Life 2013-12-21 12:46:47 UTC
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.

Comment 6 Fedora End Of Life 2014-02-05 20:35:47 UTC
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.


Note You need to log in before you can comment on or make changes to this bug.