Wednesday, May 18, 2016
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.
On Tuesday, May 17, 2016 at 11:27:22 AM UTC+5:30, Neo Elit wrote:
-- My ISP is using some **** proxy and was removing the If-None-Match headers. Tried another service and is working normally.
On Tuesday, May 17, 2016 at 11:27:22 AM UTC+5:30, Neo Elit wrote:
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/ dd8d9f22142db12cee077723b7cd8b f5
From http://stackoverflow.com/questions/18693718/weak-etags- 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:in-rails
https://gist.github.com/NeoElit/ dd8d9f22142db12cee077723b7cd8b f5
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?
You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rubyonrails-talk+unsubscribe@googlegroups.com.
To post to this group, send email to rubyonrails-talk@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-talk/b5959bf3-20e1-461d-ba0c-06ee5fcd7ba7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment