> On 6 Mar 2021, at 17:47, Sumit Kumar <sumitkumarsingh509@gmail.com> wrote:
>
>
> I am trying to develop a QUIC POC as part of my master's project and the results gained from here are also supposed to help me build a base for QUIC based Nginx adoption in Cisco's Products.
>
>
>
> I am simply trying to follow the official wiki here : https://www.nginx.com/blog/introducing-technology-preview-nginx-support-for-quic-http-3/
>
>
>
> Well, we have been able to accomplish the successful building of the code (via README). The Nginx server is up and running as of now and I see no issues there. The next pit stop is finding a successful QUIC client which I already tried all the browsers and failing to find any of them working for QUIC as of now(I tested these browsers with QUIC enabled websites).
>
>
>
> One section, where we would like your kind help for the project/PoC would be having a proper nginx.conf being displayed on the wiki page so that we can quickly set up and play with QUIC based Nginx server. As of now, I am unable to see chrome/Firefox loading localhost or 127.0.0.1/ pages with the configs mentioned in your wiki.
See https://quic.nginx.org/README for an up to date
nginx.conf example and known to work clients.
You may first ensure the client is working correctly by trying
a public HTTP/3 server such as quic.nginx.org; see also
https://github.com/quicwg/base-drafts/wiki/Implementations
>
> It says 404 as of now. (nginx.conf attached)
>
That doesn't explain much.
HTTP semantics such as status codes doesn't differ between protocol versions.
> Access log :
>
> 127.0.0.1 - - [06/Mar/2021:20:13:04 +0530] "GET / HTTP/1.1" 404 555 "-" "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/89.0.4389.72 Safari/537.36" "-" "h3-29"
>
It using HTTP/1.1 (for whatever reasons).
Usually that means a failure to negotiate HTTP/3.
--
Sergey Kandaurov
_______________________________________________
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
