UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/51.0.2704.84 Safari/537.36

Steps to reproduce the problem:
1. client js runs the following function on doucment.ready
function startAlarmLongPoll() {
    $.ajax({
        url:"/alarm",
        method:"GET",
    }).done(function(data, textStatus, jqXHR){
        startAlarmLongPoll();
        alert(data);
    }).fail(function(jqXHR, textStatus, errorThrown){
        if (textStatus == "timeout" || jqXHR.status == 408){
            startAlarmLongPoll();
        }
    })
}
2. The server uses cookies to store session that includes a webtoken with expiry time. Some requests from the client js file renew the token which is saved to session in response to the request.
3. The long poll function above never sees the 408 from the server, the browser automatically resends the request, BUT with the old session with non renewed token
4. The server times out because of the session containing expired token when the long poll request is resent by the browser 

What is the expected behavior?
The browser updates the cookie it holds on every response. This updated cookie is sent for subsequent requests.The automatic browser re-sends of the GET \alarm request should send this updated cookie, not the original old cookie

What went wrong?
Server times out because of the unrenewed token

Did this work before? N/A 

Chrome version: 51.0.2704.84  Channel: stable
OS Version: OS X 10.11.5
Flash Version: Shockwave Flash 21.0 r0

Works in Safari