Replies: 2 comments 2 replies
-
My guess is nginx only supports an HTTP/1.1 proxy backend and it's probably not configured with the correct hostname. Can you share the entire Nginx configuration? |
Beta Was this translation helpful? Give feedback.
2 replies
-
The solution is here phusion/passenger#2522 |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi there!
While testing HTTP/3 + QUIC with a patched version of Nginx in a development server, I realized there are some things that break web apps.
Checking logs from Nginx, it seems that it handles the protocol pretty good; checking logs and output from Rails app reveals that HTTP/3 isn't handled properly e.g.
Entry in Nginx access log:
<client_ip> - - [<datetime>] "GET / HTTP/3.0" 200 <bytes> "<referer>" <client>
Values taken from request.env on Rails app
So I think something's not working properly on request processing: Protocol and hostname are taken as localhost and HTTP1.1 from second request onwards. Due to that, some internal links (e.g. Active Storage redirection links to blobs) and asset urls (e.g. Propshaft links to static assets) break down because host is taken as "127.0.0.1:3000".
I'd like to note that I'm not a Ruby nor Rails expert, so I don't know whether this problem must be discussed here or in some other part (perhaps Passenger or Rails). Any feedback given will be pretty much appreciated, although I know it can be too early to talk about QUIC - HTTP/3 support.
Thanks in advance!
Beta Was this translation helpful? Give feedback.
All reactions