MooTools Depender, Safari, etags and 412 Precondition Failed

Posted on by 
/**
* This replaces the default MooTools more Depender.request function to use
* HTTP "get" rather than "post".
*
* When sending requests for files via the depender, I was finding that Safari
* wasn't getting and re-evaluating them the second time I visited the page.
* This was because an etag was sent with each script.
*
* Safari responds to etags properly and adds "If-None-Match" and
* "If-Modified-Since" headers to another request for the same file. This makes
* Apache respond with a 412 status (Precondition Failed) as it should do for
* "post" requests (according to RFC 2616).
*
* Unfortunately Safari doesn't then deal with the 412 as it does with a 304
* (Not Modified). It doesn't grab what it has in the cache and put it in the
* response, it gives you nothing.
*
* For "get" requests, Apache has to respond with a 304, or 200 or whatever, but
* not 412. So we change the request method so we don't have to deal with 412.
*/
Depender.request = function(url, callback){
    new Request.JSON({
        url: url,
        secure: false,
        onSuccess: callback,
        method:'get'
    }).send();
};

24,935 thoughts on “MooTools Depender, Safari, etags and 412 Precondition Failed”

  11. I believe everything published made a lot of sense.
    But, think on this, suppose you were to write a awesome post title?

    I am not suggesting your content is not solid, however what if you added a title that grabbed people’s attention? I mean MooTools Depender, Safari, etags and 412 Precondition Failed | freestyle
    developments is a little plain. You could look at Yahoo’s front page
    and note how they create article headlines to get people to open the links.
    You might add a video or a picture or two to get readers interested about what you’ve
    got to say. Just my opinion, it would bring your posts a little
    bit more interesting.