Rails 4.2.6 fresh_when not functioning properly in passenger-standalone production

Neo_Elit · May 17, 2016, 5:57am

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.

gist.github.com

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

localhost_headers

#Request headers---------------------------------
Host: localhost:3000
User-Agent: Mozilla/5.0 (X11; Ubuntu; Linux i686; rv:45.0) Gecko/20100101 Firefox/45.0
Accept: text/html, application/xhtml+xml, application/xml
Accept-Language: en-US,en;q=0.5
Accept-Encoding: gzip, deflate
X-XHR-Referer: http://localhost:3000/business
Referer: http://localhost:3000/business
Cookie: ******************************************
Connection: keep-alive

This file has been truncated. show original

server_headers

#Request headers------------------------------------
Host: test.gridlle.com
User-Agent: Mozilla/5.0 (X11; Ubuntu; Linux i686; rv:45.0) Gecko/20100101 Firefox/45.0
Accept: text/html, application/xhtml+xml, application/xml
Accept-Language: en-US,en;q=0.5
Accept-Encoding: gzip, deflate
X-XHR-Referer: http://test.gridlle.com/business
Referer: http://test.gridlle.com/business
Cookie: *************************************
Connection: keep-alive

This file has been truncated. show original

static_pages_controller.rb

class StaticPagesController < ApplicationController
  
  def business
    fresh_when(etag: "c2fd5566bdfc7e3dca4c74a4156321d85b19d5a50073d525d4b2ba010d0365c3", last_modified: DateTime.parse("2016-05-16T16:19:48+00:00"))
  end
  
end

From http - Weak ETAGs in Rails? - Stack Overflow 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: HTTP Cache · GitHub

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?

Neo_Elit · May 18, 2016, 4:37pm

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.