TiddlyWiki.org

WikiTimelineRoadmapBrowse SourceView TicketsSearchSimile Timeline

Ticket #536 (closed defect: fixed)

Opened 5 months ago

Last modified 5 months ago

nocache addition to url in doHttp core function is misunderstood by some web servers

Reported by: jayfresh Assigned to: jayfresh
Priority: trivial Milestone:
Component: core Version:
Severity: low Keywords: xhr nocache
Cc:

Description

In doHttp(), ?nocache=<random number> is added to any url that is requested. If you try, for example, http://www.google.com/?nocache=0.26112940326703693, that returns a 404.

Attachments

ticket536.patch (1.5 kB) - added by jayfresh on 25/03/08 21:06:47.
Patch for ticket 536

Change History

25/03/08 21:06:47 changed by jayfresh

  • attachment ticket536.patch added.

Patch for ticket 536

25/03/08 21:06:58 changed by jayfresh

  • owner changed from JeremyRuston to jayfresh.
  • status changed from new to assigned.

25/03/08 22:04:20 changed by XavierVerges

The supposed way (?) to control the cache is with the 'cache-control' header

http://www.w3.org/Protocols/rfc2616/rfc2616-sec13.html#sec13 (Caching in http) http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.9 (cache-control header)

However, this is something I wrote in 2006: I believe that Firefox is caching too much for XMLHttpRequests that set the 'cache-control' header on a GET request to 'no-cache' or 'no-store'. In my opinion, Firefox should not be using the cache for these requests, but it is.

and I ended up using the ?nocache= trick :-( I tried again the same experiment, using the Live Http Header extension, and two years later, Firefox's cache is still too agressive imo

31/03/08 15:15:56 changed by JeremyRuston

  • status changed from assigned to closed.
  • resolution set to fixed.

Fixed in changeset:4202

Meta

Visit the Trac open source project at
http://trac.edgewall.org/