Images served via URLs with params (?....) are never cached

VERIFIED WORKSFORME

Status

()

Core
Networking: Cache
VERIFIED WORKSFORME
16 years ago
13 years ago

People

(Reporter: Marc Spencer, Assigned: gordon)

Tracking

Trunk
PowerPC
Mac OS X
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

16 years ago
Dynamically generated images are never cached, regardless of cache settings.
While it makes sense to never cache document urls containing arguments (or does
it), image tag URLs containing arguments should be cached.

Comment 1

16 years ago
Marc, what build ID are you reporting this bug against? Please provide an
example URL.
(Reporter)

Comment 2

16 years ago
Build info:

Mozilla 1.1
Mozilla/5.0 (Macintosh; U; PPC Mac OS X; en-US; rv:1.1) Gecko/20020826

Sample URL:

http://some.server.com/someuri?arg1=key1[value1],key2[value2]&arg2=key3[value3] ...

Except it's properly escaped, as in:

http://some.server.com/someuri?arg1=key1%5Bvalue1%5D,key2%5Bvalue2%5D ...

I agree Moz shouldn't cache if the response has pragma: no-cache set, but it
doesn't, I checked.

Comment 3

16 years ago
Marc, please also test in a more recent build such as 1.2a or a current nightly.
(Reporter)

Comment 4

16 years ago
I tried in 1.2a

Not better, worse even, as the dragon starts moving and never stops when one of
these images are loaded from a URL containing arguments.

Comment 5

16 years ago
Marc, by example URL, I meant one that really works.
-> networking:cache
Assignee: asa → gordon
Component: Browser-General → Networking: Cache
QA Contact: asa → tever

Comment 7

15 years ago
Marc, can you reproduce this problem using a current nightly build? Also, we're
still waiting on that example URL from you.
Summary: Images served via URLS with params (?....) are never cached → Images served via URLs with params (?....) are never cached

Comment 8

14 years ago
no response-->resolving wfm
Status: UNCONFIRMED → RESOLVED
Last Resolved: 14 years ago
Resolution: --- → WORKSFORME

Updated

13 years ago
Status: RESOLVED → VERIFIED
QA Contact: tever → benc
You need to log in before you can comment on or make changes to this bug.