express returns 304 for IE repeative requests

Question

I'm experiencing some strange behavior of ExpressJS. On second request to my node.js/express based API URL it always returns 304 Not Modified response code to IE. Other browsers get 200(Chrome/FF). The problem is, that it returns 304 even if the content actually has been changed. I tried to search, and couldn't find anything on the topic. Also I tried to find a difference in requests headers of IE and Chrome, and could see any header that may cause that. Any help will be appreciated.

I have to add the connection goes via SSL, in case it matters

How are you determining what response code IE gets? – josh3736 Aug 30 '12 at 22:41 — josh3736, Aug 30 '12 at 22:41
josh3736, I'm checking network log in IE Developer Tools – bbbonthemoon Aug 31 '12 at 07:58 — bbbonthemoon, Aug 31 '12 at 07:58

score 6 · Answer 1 · edited May 23 '17 at 12:34

The Cache-Control header is a workaround. The bug is in internet explorer's interpretation of the HTTP 1.1 spec for the header.

I added this to my route handler, which solved the problem. You also need a Last-Modified or ETag header, but express was already sending that for me.

res.setHeader("Expires", "-1");
res.setHeader("Cache-Control", "must-revalidate, private");

See: Make IE to cache resources but always revalidate

score 5 · Answer 2 · answered Jan 11 '13 at 10:32

Having the same problem I look a lot around and it turns that in fact the problem comes from a stupid aggressive caching of ajax get requests by IE. In fact when you see this 304, the actual request never hits the server but IE responds with the latest data from his cache. This is intended behavior by MS, and thus there are only workarounds.

My preferred is to attach to each ajax get request a useless query parameter containing the current time. It will force IE to always retrieve from the server. The nice part is if you use jQuery, you can configure it to this automatically with

$.ajaxSetup({cache:false})

Another work around is to use POST requests instead of GET, but this is not always an option.

Why does IE lie and say it got a 304? Stupid things like that are what makes working with IE an absolute pain... — Jasper, Oct 23 '18 at 14:26
Also: don't misuse POSTs for this as that's just mis-implementing a HTTP method. Instead, go with the timestamp solution or the Cache-Control solution. — Jasper, Oct 23 '18 at 14:28

score 3 · Answer 3 · answered Aug 31 '12 at 20:31

3

Well, I managed to fix it by adding Cache-Control header

answered Aug 31 '12 at 20:31

bbbonthemoon

1,760
3
19
31

That's more of a workaround. Hopefully someone can post a solution. – Brad Aug 31 '12 at 20:35

express returns 304 for IE repeative requests

3 Answers3

Linked