Live data from Hacker News

Show HN: Nginx Image with HTTP/3 (QUIC), TLS1.3 with 0-RTT, Brotli

news.ycombinator.com

41–50 of 69 posts

Re: Show HN: Nginx Image with HTTP/3 (QUIC), TLS1.3 with 0-RTT, Brotli

#41
post #11
post #4

Yay! Nothing better than to put something that screams "bleeding edge" to handle all your traffic. YOLO, amirite? update: I love the unexplained downvotes, can't help but feel that as there's no argument they can make against what I wrote they are implicitly acknowledging that the point I made is, as it happens, correct.

I'll explain it, if you'd like. Correct, no one is making an argument against what you said, because everyone understands that point. For most people, it doesn't need to be said. No one is ripping out production infrastructure and replacing it with this image. There's no comment anywhere suggesting it. What you're doing is called "preaching to the choir". You're trying to be a contrarian to show everyone how smart an…

Please don't respond to a bad comment by breaking the site guidelines yourself. That makes this place strictly worse. Crossing into personal attack, which you did here and downthread (https://news.ycombinator.com/item?id=21308653) is particularly bad and the sort thing we ban accounts for, even if another comment was provocative.

We're really trying to avoid flamewars here, for the same reason that cities avoid flaming buildings. If you'd respect that in the future we'll be grateful.

https://news.ycombinator.com/newsguidelines.html

Re: Show HN: Nginx Image with HTTP/3 (QUIC), TLS1.3 with 0-RTT, Brotli

#42
post #36
post #4

Yay! Nothing better than to put something that screams "bleeding edge" to handle all your traffic. YOLO, amirite? update: I love the unexplained downvotes, can't help but feel that as there's no argument they can make against what I wrote they are implicitly acknowledging that the point I made is, as it happens, correct.

Your comment is correctly getting downvoted because it broke both the site guidelines and the Show HN guidelines: https://news.ycombinator.com/newsguidelines.html https://news.ycombinator.com/showhn.html Would you mind reading those and taking the spirit of this site to heart when commenting here? We're trying for a bit better than internet default, and sarcastic dismissals push things in the wrong direction. Your co…

OK, will do, I'm sorry the discussion went off the rails like this. Rest assured that while the form wasn't the most neutral, the intent was definitely the best possible and absolutely no malice was intended, contrary to the forced interpretations that were given in the responses.

Re: Show HN: Nginx Image with HTTP/3 (QUIC), TLS1.3 with 0-RTT, Brotli

#43
I would suggest highlighting the experimental nature of the repo, especially if someone reaches it without going through HN. I've read the catchy "All built on the bleeding edge. Built on the edge, for the edge." but IMO it doesn't really sound like a warning that this may not be suitable for serious production use.

Re: Show HN: Nginx Image with HTTP/3 (QUIC), TLS1.3 with 0-RTT, Brotli

#45
post #42
post #36

Earlier quoted context omitted.

Your comment is correctly getting downvoted because it broke both the site guidelines and the Show HN guidelines: https://news.ycombinator.com/newsguidelines.html https://news.ycombinator.com/showhn.html Would you mind reading those and taking the spirit of this site to heart when commenting here? We're trying for a bit better than internet default, and sarcastic dismissals push things in the wrong direction. Your co…

OK, will do, I'm sorry the discussion went off the rails like this. Rest assured that while the form wasn't the most neutral, the intent was definitely the best possible and absolutely no malice was intended, contrary to the forced interpretations that were given in the responses.

Rephrased the post as https://news.ycombinator.com/item?id=21308812, hopefully we should be good now.

Re: Show HN: Nginx Image with HTTP/3 (QUIC), TLS1.3 with 0-RTT, Brotli

#46
post #12

Earlier quoted context omitted.

Thanks for the labels. Appreciated how you put me in my rightful place. Sorry if I'm being such a joy killer. I guess I've been witness to too many failures for not feeling to call this out before someone gets burned. Oh right, but no one needs to be told to be careful, right... No one is here to learn anything, as we all already know everything. Makes you wonder what's the point of showing something new in the first…

> Does the readme say anywhere "experimental, not for prod use"? "Built on the edge, for the edge" It's pretty obvious it's an experiment. It's reasonable of the author to assume anyone running serious production infrastructure will be prudent enough to not just blithely go ahead and implement this. Even if it isn't, you could calmly suggest the author add more warnings to the readme. A project like this is no place…

> A project like this is no place for that kind of rage.

I can assure you absolutely no rage was intended, or expressed, in my first message. Was the comment needlessly snarky? Yes. Was it anything beyond that? Absolutely not, and I would appreciate if this didn't get further blown out of proportion. I already apologized for the form of the comment.

Re: Show HN: Nginx Image with HTTP/3 (QUIC), TLS1.3 with 0-RTT, Brotli

#47
post #33

OT: musl is pronounced like 'muscle' or do you spell it out 'm-u-s-l'

>It’s pronounced the same as the English words “mussel” or “muscle”. musl is small like one but powerful like the other.

https://www.musl-libc.org/faq.html

The logo is a mussel :)

Re: Show HN: Nginx Image with HTTP/3 (QUIC), TLS1.3 with 0-RTT, Brotli

#48
post #22

Earlier quoted context omitted.

I think it will be better to fully disable early data for people without full control of DC's network equipment. I don't know why Cloudflare made a decision about using headers and Too Early response. They have full control of their POPs. It will be better to measure RTT and use UDP based KV storage with tickets only for clients with high RTT. So for clients with RTT higher then access to KV storage it will be better…

> It will be better to measure RTT To measure RTT you need to perform a round trip. Hence the name. But the _whole point_ of this feature is to avoid incurring the cost of an extra round trip if possible.

There is no need to send extra data to measure RTT. On the TCP handshake SYN/ACK you already know RTT. Linux kernel provides this info in tcp_info data structure.

Re: Show HN: Nginx Image with HTTP/3 (QUIC), TLS1.3 with 0-RTT, Brotli

#49
From WP I get the impression that the work-in-progress now called HTTP/3 was not necessarily designed supposed to supplant HTTP/2:

> On 28 October 2018 in a mailing list discussion, Mark Nottingham, Chair of the IETF HTTP and QUIC Working Groups, made the official request to rename HTTP-over-QUIC as HTTP/3 to "clearly identify it as another binding of HTTP semantics to the wire protocol ... so people understand its separation from QUIC"

Any opinions on how things are likely to play out?

Re: Show HN: Nginx Image with HTTP/3 (QUIC), TLS1.3 with 0-RTT, Brotli

#50
post #18

I'm just curious, is there a reason not to use a multi-stage docker build here? There are a ton of build steps, and it seems pretty tedious to have to start from scratch every time while developing the image without any layer caching.

Hi, my main task this weekend was to get it fully working. I will break down the steps over this week to utilize cache layers. I will try to get it done hopefully this week or by the weekend depending on work. Thanks a lot for your feedback.

Might I suggest you use Skaffold for this task, which can work with regular Docker as well.
Post reply on HN