Bug Tracker

Changes between Initial Version and Version 1 of Ticket #8095, comment 1


Ignore:
Timestamp:
Jan 31, 2011, 6:00:14 AM (9 years ago)
Author:
jaubourg
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #8095, comment 1

    initial v1  
    22
    33Current behaviour makes perfect sense:
    4 1) hashmap key must be the full url with parameters (your "solution" didn't include the data into the cache_key),
    5 2) If and when, cache is set to false, the anti-cache parameter is part of the full url and, thus, data is always pulled from the server and no 304 will ever be issued, which is actually exactly what the cache option is supposed to ensure.
     4* hashmap key must be the full url with parameters (your "solution" didn't include the data into the cache_key),
     5* If and when, cache is set to false, the anti-cache parameter is part of the full url and, thus, data is always pulled from the server and no 304 will ever be issued, which is actually exactly what the cache option is supposed to ensure.
    66
    77So, if you want to use ifModified and get 304 responses, just don't set the cache option to false.