Use of Cache-Control can be difficult in browsers

[quentez]

When performing XHR requests within the first second* of a page refresh, some browsers will override the Cache-Control header for those requests.

In FF, max-age=0 is appended.
In Chrome, max-age=0 replaces whatever was set when building the XHR.

This makes it difficult to make tent requests that require proxy or no-proxy as their Cache-Control value during that critical time frame.

I suggest moving away from the Cache-Control header and either use a custom header (something like X-Tent-Cache-Control) or anything else that doesn't involve something the browsers could meddle with.

* : Approximately, depends on the browser and doesn't appear to be a constant.

[jvatic]

This appears to only occur when reloading the page. Chrome's behavior of completely replacing the Cache-Control header is problematic.

[quentez]

Yep, only when reloading. I'll try to see if Safari/IE have similar behaviors.