How does "304 Not Modified" work exactly?
How are "304 Not Modified" responses generated?
How does a browser determine whether the response to an HTTP request is 304?
Is it set by the browser or sent from the server?
If sent by the server, how does the server know the data available in cache, also how does it set 304 to an image?
My guess, if it's generated by the browser:
function is_modified()
{
return get_data_from_cache() === get_data_from_url();
}
function get_data_from_cache()
{
return some_hash_or_xxx_function(cache_data);
}
function get_data_from_url()
{
return some_hash_or_xxx_function(new_data);
}
function some_hash_or_xxx_function(data)
{
// Do something with the data.
// What is that algorithm?
return result;
}
console.log(is_modified());
I am relying on a third party API provider to get data, parse & push it to my database. The data may or may not change during every request, but the header always sends 200. I do not want to parse, check the last Unique ID in DB and so on... to determine the change in data, nor compare the result directly rather I md5(), sha1() and crc32() hashed the result and works fine, but I'm wondering about the algorithm to determine 304.
I want to use the same kind of algorithm to determine the change in my data.
When the browser puts something in its cache, it also stores the Last-Modified or ETag header from the server.
The browser then sends a request with the If-Modified-Since or If-None-Match header, telling the server to send a 304 if the content still has that date or ETag.
The server needs some way of calculating a date-modified or ETag for each version of each resource; this typically comes from the filesystem or a separate database column.
Last-Modified : The last modified date for the requested object If-Modified-Since : Allows a 304 Not Modified to be returned if last modified date is unchanged. ETag : An ETag is an opaque identifier assigned by a web server to a specific version of a resource found at a URL. If the resource representation at that URL ever changes, a new and different ETag is assigned. If-None-Match : Allows a 304 Not Modified to be returned if ETag is unchanged.
the browser store cache with a date(Last-Modified) or id(ETag), when you need to request the URL again, the browser send request message with the header:
https://i.stack.imgur.com/CxmDR.png
the server will return 304 when the if statement is False, and browser will use cache.
Follow WeChat
Success story sharing
Want to stay one step ahead of the latest teleworks?
Subscribe Now相似问题
- Detect when a browser receives a file download
- Should HTTP 304 Not Modified-responses contain cache-control headers?
- Why am I getting "(304) Not Modified" error on some links when using HttpWebRequest?
- How does HTTP file upload work?
- Why is it common to put CSRF prevention tokens in cookies?
- What is the "Upgrade-Insecure-Requests" HTTP header?
ETagis the keyword, checked with headersETagremains same in bothResponse Headers&Response Headers From Cache, can you tell the algorithm behindETag. I have updated my question stating my requirement.ETagis just a field where the server can store a unique ID (typically a hash or version number or vector clock). It doesn't help you calculate that ID at all; that's up to your server-side code.max-agethen does the browser need to make the request? (as it could stub in 304 and not make the request at all)... you want this e.g. with "fingerprinted" assets (they're good forever). Else what's the point ofmax-age...