5 ms·
Over the last few months we've seen so many "Page served from..." and most of them are just DOA. Why can't people put a little effort and host those pages on t
by freitasm 4y ago
Over the last few months we've seen so many "Page served from..." and most of them are just DOA.
Why can't people put a little effort and host those pages on their hardware/software of choice but at least put them behind some CDN (at least for static resources)?
- tssva 4y agoBecause when people do serve them from behind a CDN people rush to the comments to lambast them for not serving every request from the system in question.
- aaronk6 4y agoThis. Part of the challenge for me was to avoid any proxies and and have all requests go directly to the ReactOS system. I’m totally aware that this doesn’t make any sense in a real-world scenario.
- Wowfunhappy 4y agoWhich, I mean, I think is fair tbqh.
- pessimizer 4y agoMaybe it wasn't meant for HN, but actually for someone's blog that only gets a few hundred hits a day if it's a very successful blog. Going out on a limb here.
- girvo 4y agoThis is HN’s fault this time: it’s forcing HTTPS which the site doesn’t support. Try this, and it’ll work: http://reactos.aaron.cc/ http://reactos.aaron.cc/
- math-dev 4y agoSurely in this day and age one would set up https, that too on a website related page
- Tao3300 4y agoJust for this there would be no point.
- chmod775 4y agoPossibly SSL is not something that's quite that easy to set up on ReactOS yet? Probably doesn't have a letsencrypt client. Maybe there's no SSL/TLS library that works on it at all.
- johnisgood 4y agoMaybe someone can put Forth into it. :)
- aaronk6 4y agoHi, I’m the author of the page. > Probably doesn't have a letsencrypt client. Right, Certbot doesn’t work because of an issue with Python, however, it’s easy to generate the certificates elsewhere and inject them into the virtual machine. > Maybe there's no SSL/TLS library that works on it at all. There is, but the OS needs to be patched to fix a socket issue (see https://github.com/reactos/reactos/pull/4086 https://github.com/reactos/reactos/pull/4086 which was never merged because of side effects). The patch does seem to work for my use case and I had actually the site running on HTTPS, but a few hours later it become unresponsive. I didn’t realize that this was probably just due to the HN DOS. I will give HTTPS another shot later today.
- fishtacos 4y agoThere was an attempt: https://reactos.org/forum/viewtopic.php?f=4&p=146310 https://reactos.org/forum/viewtopic.php?f=4&p=146310
- deaddodo 4y agoIt literally says on that static page of no security consequence that they tried to set it up, but it couldn’t negotiate a handshake without stalling.
- Mo3 4y agoThat doesn't work for me either.
- indymike 4y agoHalf the time it's the links says https and the server only does http.
- deleted 4y ago[deleted]
- nine_k 4y agoI think people who make these pages neither anticipate nor aim for getting to the front page of HN or other large audience. This us why they don't spend time setting up.Cloudflare and such. Then somebody posts a link, which, against all odds, gets enough upvotes, et voilà, their hardware is melting under the load
- aaronk6 4y agoExactly! I had only posted the link on www.reddit.com/r/reactos and didn’t expect it to get attention from a wider audience :-) Also, I deliberately avoided CDNs and caches to see if the source system can handle the load. I know that this woudn’t make any sense in real-world scenario, but for this project, this was part of the fun.
- dopp0 4y agobecause the intent of the post is exactly to show that it can be served, not that it can handle a huge amount of traffic HN causes.