MooTools Depender, Safari, etags and 412 Precondition Failed

/**
* 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

  1. I do consider all the ideas you have introduced in your post.
    They’re really convincing and will certainly work. Nonetheless, the posts are too short for novices.
    May you please prolong them a little from next time?
    Thank you for the post.

  2. I was wondering if you ever considered changing the page layout of
    your website? Its very well written; I love what youve got to say.

    But maybe you could a little more in the way of content so people could connect with it better.
    Youve got an awful lot of text for only having one
    or 2 pictures. Maybe you could space it out better?

  3. Having reviewed plenty of online casinos over the years,
    here is a list of common bonuses and some helpful tips on how to make
    the most of your $10 deposit.

  4. Hi! I could have sworn I’ve visited this blog before but after looking at many of the articles
    I realized it’s new to me. Anyhow, I’m certainly pleased I found it and I’ll
    be bookmarking it and checking back frequently!