The indentation is formatting to give a clear delineation between various sections, such as each feature/fix/item of the changelog. Which makes it easier to read rather a run along blob of text with no clear markers.
You see this same indentation with un/ordered lists in HTML or word documents.
I'm surprised HN hasn't added a feature where if you start a comment with "I'm surprised" it asks you to tick a box to confirm that you're really sure you're contributing to the discussion.
I am strongly in favor of this. I would also like HN to implement a warning that your comment may be extremely uninteresting if it starts out with, "Unfortunately..." or, "Can we all just agree that..."
Why surprised? It's rock solid, stable, fast, and does pretty much everything you need, and nothing is hidden behind premium tiers, unlike nginx where they leave bugs and awful behaviour in the open source version that aren't in the premium ones (e.g. nginx used to only resolve hostname entries on start-up, https://forum.nginx.org/read.php?2,215830,215832#msg-215832, so if you used a hostname in proxy_pass, and the DNS changed, oops sorry. Actual honouring of DNS TTLs used to be a premium only feature)
I love apache as much as anyone, cut my teeth with it and still work with it plenty.
It doesn’t strike me as odd to question its fit for people who have more experience with containers. If there’s a reverse proxy in the front, one may just need business logic in the back.
I am actively trying to remove apache from a large chunk of projects mainly because at this point it is being used as a poor reverse proxy and not a web server which is its core competency.
I run all my microservices and web sites in containers behind Apache. It's not required to use any specific reverse proxy, nginx is Russian made, like Jetbrains' products so Google pushes them and that's why under-educated milenials assume nginx is the only reverse proxy on Earth.
It's still in most distros default repos, unlike things like caddy, and also supports features like mod_ldap out of the box without enterprise, like nginx. If you just need a simple web server, potentially with some auth even for static files its a no brainier default for internal projects.
46 comments
[ 3.3 ms ] story [ 114 ms ] threadHTTP/2 Rapid Reset and Apache
https://github.com/icing/blog/blob/main/h2-rapid-reset.md
Apache httpd 2.4.58
https://github.com/icing/blog/blob/main/httpd-2.4.58.md
<https://news.ycombinator.com/item?id=37830987>
<https://news.ycombinator.com/item?id=37830998>
<https://news.ycombinator.com/item?id=37831004>
HTTP/2 Rapid Reset: deconstructing the record-breaking attack - https://news.ycombinator.com/item?id=37831004 - Oct 2023 (23 comments)
HTTP/2 zero-day vulnerability results in record-breaking DDoS attacks - https://news.ycombinator.com/item?id=37830998 - Oct 2023 (71 comments)
The novel HTTP/2 'Rapid Reset' DDoS attack - https://news.ycombinator.com/item?id=37830987 - Oct 2023 (106 comments)
The link is to a plain text file.
The indentation is formatting to give a clear delineation between various sections, such as each feature/fix/item of the changelog. Which makes it easier to read rather a run along blob of text with no clear markers.
You see this same indentation with un/ordered lists in HTML or word documents.
It doesn’t strike me as odd to question its fit for people who have more experience with containers. If there’s a reverse proxy in the front, one may just need business logic in the back.
I'm trying to imagine what that haircut would look like
This attack is just about failing to enforce the negotiated parameters during the start phase of the connection.
From the README of the apache_1.3.0 distribution (April 1998) https://archive.apache.org/dist/httpd/
Love this project. It changed the world and it still goes strong. The closest to "forever software"?