Hi John, Two things:
1) Make sure you're not doing a browser refresh when testing your setup as this will send the cache invalidate request header to your server which will bypass any conditional get logic you have (though this does vary by browser) 2) I've seen the browser be the culprit many times in situations like these. I.e. sometimes it sends cache-busting headers and sometimes it does not. I just tried your URL out in Chrome a few times and it was NOT honoring the conditional GET. Then I turned on the Chrome dev tools pane and it started honoring the conditional. I've seen similar stuff in FF. So... as of right now it looks like your conditional GET is working (for me, see response headers: http://cl.ly/5Spf). However, not sure if you did some additional tweaking after your initial posts. Also - you're correct - Varnish should not be at play here as the only way to know if a conditional get has expired is to check the backend for new etag/last-modified attributes. -Ryan Daigle Heroku -- You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
