Ajax ifModified has problems
|Reported by:||schickb||Owned by:|
When ifModified is set, jQuery adds its own If-Modified-Since header (and the first ajax call for each url gets a bogus old 1970 date). Shouldn't the handling of If-Modified-Since be left to the browser which will already be caching URLs and modified dates between sessions (unlike jQuery)? Also browser support Etag validation, and this actually works correctly now since jQuery doesn't mess with the If-None-Match header as it does with the If-Modified-Since header.
It seems like the ifModified option should do nothing more than control whether or not jquery processes the response data and calls success.
Although it is already rather odd that jQuery calls the error handler when ifModified is true and the data is unchanged. Maybe there should be a 3rd "unchanged" callback for ajax requests.