You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a fairly simple Sinatra app that makes use of send_file for GET and HEAD requests to a given path. The HTTP client side depends on asking a HEAD request before getting a file. For GET requests, the response headers look normal:
I'd like to call out this issue as a wonder one. The failing test case made it so easy for me to figure out what was wrong and correct the issue in only about 5 minutes.
I had a user reporting that (sometimes) they viewed the source code of the website. Sometimes HTML, sometimes the JavaScript AJAX response. This seemsed to have been caused by using the back button and caches etc...
I've never found a way to reproduce this reliably (although I've seen this myself), but it occured in different browsers (Firefox, Chrome at least) and different OS (linux, windows).
Could this problem been caused by this?
My setup is (F5) -> nginx -> Puma (rails 3.2)
Note that F5 was not always present.
I thought I already posted this, so if I posted thissomewhere else my apologies...
Hi!
I have a fairly simple Sinatra app that makes use of
send_file
for GET and HEAD requests to a given path. The HTTP client side depends on asking a HEAD request before getting a file. For GET requests, the response headers look normal:Both in Puma 2.1.x & 2.2.x, the response to the HEAD request is missing the content related information in its headers:
Interestingly enough, in Puma 2.0.1 (or WEBRick) the HEAD response is OK:
I'm able to reproduce this behaviour using the latest
master
and adding a new test undertest/test_puma_server.rb
Env info:
Note:
The text was updated successfully, but these errors were encountered: