Live data from Hacker News

Do svidaniya, Igor, and thank you for Nginx

nginx.com

61–70 of 366 posts

Re: Do svidaniya, Igor, and thank you for Nginx

#61
post #45

Earlier quoted context omitted.

The performance engineering in NGINX back then was really quite something. This classic 2007 tutorial starts by pointing out that NGINX parses the HTTP verb by looking at the second letter first, so that if it's O it knows to check for POST or COPY! https://web.archive.org/web/20070505051653/http://www.riceon...

Doing Boyer and Moore proud. I think that if you want to support all verbs, you face at least 3 'ambiguities' whether you first check the first, second, or third character of the string. (It must be at most the third, as the shortest verbs are 3 characters long.) First checking the first character is ambiguous between POST , PUT and PATCH . First checking the second character is ambiguous between HEAD , DELETE , and…

Seems likely an optimal algorithm could probably get there just looking sequentially at the first three letters in order. Would be an interesting code-golf.

Re: Do svidaniya, Igor, and thank you for Nginx

#62
post #49

unrelated but ive always thought the F5 acquisition of NGINX made little sense. I think F5 saw the writing on the wall a little late, panicked, and bought the first competitor they could come up with that showed up in a Gartner quadrant. so much of the NGINX product that aligns with F5 as a competitive element is essentially already implemented and free by people who are already completely competent in load balancing…

iRule are the things that makes the F5 appliance special, it enables you to run TCL on a variety of events (ex: HTTP_REQUEST, CLIENT_CONNECTED...). Some typical uses are requests and responses modification, logging, bug fixes on closed source web applications... I also the F5 device support various permissions levels to enable delegation/separation of administrative privileges.

Re: Do svidaniya, Igor, and thank you for Nginx

#63
post #47

Earlier quoted context omitted.

Cloudflare uses a heuristic trust model where it pulls multiple trust signals from the client. It can use several things (including stable IP address, cookies, and I think even a bit of JavaScript grabbing a nonce from local storage). If you run with a lot of "identity fuzzers" (browsing through Tor, JavaScript off, cookies banned), Cloudflare can't build its trust heuristics and needs to challenge-response more ofte…

They are breaking the web, plain and simple. Google with AMP, Cloudfare with their idiotic capchas.

No server is obligated to vend my client data.

More importantly: no server is obligated to vend data until it falls over and dies, depriving all users access to that data if it isn't mirrored.

I think Cloudflare has honestly done an admirable job of coming up with a novel solution to the problem of loadbalancing and traffic-shedding in a world with a small-but-persistent percentage of hostile actors.

Re: Do svidaniya, Igor, and thank you for Nginx

#64
post #4

Here are relevant Russian discussions on OpenNET[0] & LOR[1]. N.B. From Nginx company history on Wikipedia: > On 12 December 2019, it was reported that the Moscow offices of Nginx Inc. had been raided by police, and that Sysoev and Konovalov had been detained. The raid was conducted under a search warrant connected to a copyright claim over Nginx by Rambler—which asserts that it owns all rights to the code because it…

Was the case resolved? Wikipedia doesn't provide any further information?

You can find a summary at https://tadviser.com/index.php/Company:Nginx

TL;DR: the Russian investigators closed the case of Rambler Group against Nginx/T5 in 2020 "for the absence of a crime event". Another company co-owned by the same owner of Rambler Group started a case in the USA but it was dismissed by a court in California in 2021.

Re: Do svidaniya, Igor, and thank you for Nginx

#65
post #4

Here are relevant Russian discussions on OpenNET[0] & LOR[1]. N.B. From Nginx company history on Wikipedia: > On 12 December 2019, it was reported that the Moscow offices of Nginx Inc. had been raided by police, and that Sysoev and Konovalov had been detained. The raid was conducted under a search warrant connected to a copyright claim over Nginx by Rambler—which asserts that it owns all rights to the code because it…

Was the case resolved? Wikipedia doesn't provide any further information?

I think the characterization on Wikipedia is also incorrect. Igor seems to have had a permission directly from the CTO to open-source the code, but 10 years later the company claimed that the CTO was not in a position to do so.

Re: Do svidaniya, Igor, and thank you for Nginx

#66
I still remember when it was new and so small a novice can review it without a headache. It was to me the answer to attacks like slowloris and C10K problem. And the config, by far much more pleasant than apache or IIS. I use it to reverse proxy all the time! Thank you Igor and best wishes.

Re: Do svidaniya, Igor, and thank you for Nginx

#67

People need to stop with this Cloudflare captcha madness. I literally accessed nginx.com a few hours ago and now it hit me with a captcha again.

Also... It's nginx.com, owned by F5. Am I the only one who thinks it's a little weird, borderline embarrassing, that they're not fronting traffic themselves? "We make the best load bouncers and web server. That's why we ... Outsourced our ingress to another company that doesn't use our load balancers and which only uses our web server as part of their stack. Let the experts deal with heavy traffic, y'know?"

Re: Do svidaniya, Igor, and thank you for Nginx

#68
post #40

Earlier quoted context omitted.

Was the case resolved? Wikipedia doesn't provide any further information?

Yes, Wikipedia -- in broad strokes -- just sucks, check what happened to the Scottish Wikipedia (but there are any number of issues in the English one as well, the "no credentials" policy made sure scientists shun it because they don't want to endlessly argue with neckbeards with an agenda). Anyways, https://tadviser.com/index.php/Company:Nginx everything is dropped in Russia, there's a lawsuit in the US but at first…

Thank you. This was a great source.

Re: Do svidaniya, Igor, and thank you for Nginx

#69
post #45

Earlier quoted context omitted.

The performance engineering in NGINX back then was really quite something. This classic 2007 tutorial starts by pointing out that NGINX parses the HTTP verb by looking at the second letter first, so that if it's O it knows to check for POST or COPY! https://web.archive.org/web/20070505051653/http://www.riceon...

Doing Boyer and Moore proud. I think that if you want to support all verbs, you face at least 3 'ambiguities' whether you first check the first, second, or third character of the string. (It must be at most the third, as the shortest verbs are 3 characters long.) First checking the first character is ambiguous between POST , PUT and PATCH . First checking the second character is ambiguous between HEAD , DELETE , and…

A bit of a micro-optimization, but couldn’t you interpret 4 bytes (including the trailing null on the three-letter verbs) as a 32-bit unsigned int and then do integer comparisons or a case statement?

Re: Do svidaniya, Igor, and thank you for Nginx

#70
I know this is massively off-topic (have a good well paid "retirement" Igor), but I assumed that it would be written as

Dos Vidaniya

instead of (the correct)

Do svidanyia

My Russian studies is limited to listening to Sean Connery in The Russia House, and I guess I took Dos from the latin languages. Odd.

Post reply on HN