Rails 4.2.6 fresh_when not functioning properly in passenger-standalone production
39 views
Skip to first unread message
Neo Elit
unread,
May 17, 2016, 1:57:22 AM5/17/16
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to Ruby on Rails: Talk
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.
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
unread,
May 18, 2016, 12:37:05 PM5/18/16
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to Ruby on Rails: Talk
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.