Rails 4.2.6 fresh_when not functioning properly in passenger-standalone production

I’m trying to provide etag and last-modified headers for static page.
Locally it works fine and browser gets a 304, however on server with
passenger standalone it’s not providing a 304.

https://gist.github.com/NeoElit/dd8d9f22142db12cee077723b7cd8bf5

From http://stackoverflow.com/questions/18693718/weak-etags-in-rails
it’s
clear that even if i give strong etag it’s getting converted to weak
etag,
the browser request response headers is listed in the following gist:
https://gist.github.com/NeoElit/dd8d9f22142db12cee077723b7cd8bf5

The interesting fact is that the weak header is not even in the rails
request env. However if modify the etag from browser and send as strong
etag, it’s getting to rails env.
How can I resolve the issue so as to give a 304?

I got the issue. However the issue had nothing to do with passenger or
rails.
My ISP is using some **** proxy and was removing the If-None-Match
headers.
Tried another service and is working normally.

This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.

| Privacy Policy | Terms of Service | Remote Ruby Jobs