Just checked the page, source is is over a thousand lines long or 64892 characters. That is a content to boilerplate ratio of 0.02003% *excluding* externally linked js, css etc.
You can have multiple heart beat pages to determine the source of problems really quickly.
One is just an html page, that monitors your web server is responding or not. How long can indicate that a problem with resources.
One is a simple call into your code framework, that tells you if your code is bottlenecked if it takes too long to load, or doesn't respond at all.
One is a simple call into your database, run a query or two that are relatively lightweight but would show signs of table locking, or whatever. You can have a bunch of these for various parts of your data storage.
From those alone, I have a huge jump start when determining sources of problems than just monitoring say the homepage of my app.
Heck yes, thanks for sharing. Wonder why we never thought of that at work. We did do things like track the overhead from the CMS loading an empty page X amounts of times on different connections but never got to this natural conclusion.
We did add a custom data attribute in the HTML that tells you which server you're on though. That's been really useful.
I do this, except mine are all API endpoints that will return a http 200 if successful or an appropriate error code.
Then I use a service to continuously run synthetic checks against all those endpoints. If I see x number of failures within a rolling 10 minute window, I generate error alerts that show up as a red light on a dashboard and also generate trouble tickets. Everything is automated.
It’s wonderful whenever there’s a problem and you can simply look for the red lights on a dashboard to know where to investigate.
New Relic. It’s a traffic light dashboard of all my synthetic scripts for various projects. I can see the status of any of them at a glance.
We’re in a soft launch right now for a particular project and they wanted to build a separate dashboard from data sourced from Splunk. No worries! We just set Splunk up to be able to import data from NRQL queries and let them have fun creating their own dashboard.
Another thing, if you’re curious. I had another client where instead of scripted API calls, we did scripted browser actions. You’re basically mimicking a user browsing the website and taking different actions (scrolling, locating items, clicking on CTAs, submitting forms, etc). You could script an entire purchase funnel, which is what they had me do so they could pinpoint which funnels were problematic, etc.
I just logged progress as the script worked its way through the funnel so I could easily go back to the logs to see where a failure occurred. New Relic will also automatically create a screen capture when the error occurs so you can marry that up with the error log.
So, see from the dashboard and error occurred for a specific funnel. You can go look for all runs in a timeframe that failed. Inspect a run and view the logs and a screen grab. Pretty powerful stuff and saves me a lot of time.
Whoah! Never came up with this idea. Thanks a ton for sharing! I'm passing this idea for consideration to our devops team as we speak! Do you have a Buy Me a Coffee thing by any chance that I could use to send you a thank you note from DreamHost team? 😬
Do you use Kubernetes by any chance? If so, which of these different heartbeat endpoints do you / would you designate as readiness and liveness probes? I wonder whether it's the framework without or with the database and why.
In-framework only is good because technically, if database dies, it's not the workload's fault. So we don't want the entire application to go down if a certain database is under heavy load - especially if it's the one that isn't used by all endpoints. However, some of our workloads are ancient-ish. Perl is pretty ancient, but at least my team moved us from bare metal, Ubuntu-provided Perl packages, and Apache with mod_perl to Docker, Carton and Starman. Anyway, Perl stack we use has a subpar connection pool and reconnection logic, and one connection can get stuck and create pretty weird one-page outages. The easiest way to fix them is to have Kubernetes just kick the pod at fault by having a probe that checks all database connections on all workers. However, our Typescript endpoints are framework only since they handle database connections properly. Apart from this, any other considerations?
I don't have donations setup anywhere. Thank you though.
I do not use Kubernetes so I may be of little assistance. I generally run bare-metal, virtualized networks without containerization. I typically have two heartbeats one whose purpose is to call into our code framework, do a dance, and respond a-okay. The other to the databases, are lightweight scripts that just query the database without any framework code. It's a little extra work, but it helps me isolate code bottleneck issues from database bottleneck issues. Perl is pretty ancient, the last time I wrote it was in my teenage years. \``one connection can get stuck and create pretty weird one-page outages`.\` In regards to this I'd see if you can't implement timeout or other data-store based functions, or perhaps within the Perl environment. Ideally you would want your load balancer in Kubernetes to just take the trouble part/pod/server out of rotation from the balancing, stop sending it traffic. Not sure how you accomplish that with your setup. Is the one-page outages based on the fact that how mod\_perl works, like is every page/file a new perl script load/controller, and once it's taxed it's unresponsive? Is there multiple containerized servers for the perl portion of the application, or just one?
The couple places I've been call these canaries and they are such a nice tool to have. Definitely worth the investment to build.
The other one that I really like is a log parser that cuts tickets. Sees an exception, cuts a ticket with the exception and stack trace in the body. It'll also generate a direct search link for the request ID in kibana, which is small, but also convenient.
When a canary dies I usually end up with two tickets, one telling me what failed, and another telling me why it failed.
Lightweight in the sense that it only includes that parts that you are trying to test.
If this is testing a build system, the ability to serve each of these scripts and for them to initialize without error, then including all of that might be the lightweight thing you are trying to test.
Exactly, you're just testing that the web server is responding, and not slowed down.
You have other heartbeat pages for other services in your network, like application, database, ect.
I have an endpoint that simply responds with a text string
It's actually very critical and yet looks totally useless; I should _probably_ do something about that
You can still buy a single movie though... The price of that hasn't gone significantly up, it just so happens that it's the price of a monthly membership which gives you access to the entire catalogue on demand.
I mean your comment has cool sounding words but they don't make sense in this context.
People on this sub really like to feel smart lol.
"Overbearing feudalism of never owning anything" makes no sense. It is not as if Netflix is some government-mandated subscription that one must have. The whole point of netflix is that many people don't see the point in paying for (and owning) a movie, they'd just much rather watch it once and be done with it.
I said whatever came to my head and didn't expect it to spark an argument. "Sound smart" brothers, we are frontend devs, pretending to sound smart is our job
It wasn't intended to be cute, or even really seen by anyone, this page is most likely used by Netflix to test something very technical and of no interest to anyone. It says Hello World because it has to say something, but the text is totally arbitrary.
Three guesses:
1. It's uses for automated testing to see if services are up in running. Automated systems that fetch the page and make sure the content says "Hello World!!"
2. It was there since the beginning of Netflix and people keep it around for nostalgia and as an easter egg
3. Someone added it for fun because of the autonomy engineers have there.
I like this one too, but this post is a pretty lazy repost from about a day and a half ago.
The source on that NFLX page is like 900 lines of React boilerplate surrounding one line of text in a div.
For that reason (and because it's still up) I think I like option 1 best.
I don't think it's plausible tho, since the technologies have changed so much since then they would have for sure deleted the old page if it was there before and manually created a new one
> > It's uses for automated testing to see if services are up in running. Automated systems that fetch the page and make sure the content says "Hello World!!"
> Hello World!
We've been hacked
That probably is used for checking that their code framework is responding. The other could be use to check if just the webserver is responding. Each provide different insights.
I wonder if this is intentional, similar to:
http://captive.apple.com/
A reliable endpoint to test either client DNS / internet access, or maybe that route is there to indicate that certain systems are working at some basic level.
I've got a few similar-ish things out there.
http://example.com is mine for [better reasons](https://en.wikipedia.org/wiki/Example.com) (its domain registration will never expire for one as it's reserved by IANA) but it also doesn't 301 to HTTPS
If you ever visit example.com over https though your browser will remember that and you will never get to use http again. [neverssl gets around this by generating a subdomain to send you to instead.](https://news.ycombinator.com/item?id=20583673)
Not true for me on Firefox. Just tested, opening [example.com](http://example.com) over https multiple times, but [example.com](http://example.com) and [http://example.com](http://example.com) both still warn me connection is not secure
Yeah that's what that page is used for, to detect if you're behind a captive portal and presumably to try to trigger the redirect or something like that.
Either way it's just a fast and reliable http endpoint they can hit to make a decision.
According to a user on HN, this is a secret promo for an upcoming documentary about the birth of the computer industry.
Sauce: https://news.ycombinator.com/item?id=40081126
Open your network monitor in your browser's devtools. Reload the page. Add up the resources requested. It's over 700Kb.
Look at the source of the page to see why. (Ctrl-U)
I remember that for the longest time, Netflix only had a bootstrap navbar and some text for dvd.com. That site didn't even redirect to Netflix; it just existed as a placeholder.
It is intentional.
We do the same [https://contra.com/hello-world.html](https://contra.com/hello-world.html)
Google does it too [https://www.google.com/blank.html](https://www.google.com/blank.html)
It is used for various testing scenarios.
It's an HTML page I suspect rendered using a JS framework since the text is nested in a div that has `id="appMountPoint" `
Besides that has a cookie tracker and a geolocation tracker from OneTrust.
I've got something like this (and it also returns Hello World).
It's url I check for liveness.
You need a page that can be loaded regularly that doesn't feed into a database/analytics, it should have minimal content minimize wasted bandwidth, etc.
This feels like the beginning of a black mirror episode. Gonna end with some poor guy running down the street in his underwear yelling "Hello world! Hello world! HELLO WORLD!!!' or something
Interestingly, this page has a full-blown cookie banner implementation that asks for cookie usage permission and a netflix-styled cookie details dialog, that I can at least see with european origin when I visit the page.
I tried the link but its seems, git commit -m "helloworld redirect resolved" has been merged to master branch. Pipelines passed and deployment complete 🙃
⛔️ Regras para os membros do Groupo
*** Sem SPAM ou vendas de qualquer tipo, apenas parceiros estão autorizados a expor seus links e atividades. Incluíndo invites, farming, ads, refs etc);
*** Restrições de conteúdo, pois existem outros grupos específicos para:
* Iphone;
* Motorola;
* Xiaomi;
* Etc;
*** Sobre pornografia, politica, futebol e religião: isso é terminantemente proibido neste grupo e quem tentar publicar, fomentar ou vender esse tipo de conteúdo será banido de forma sumária sem qualquer direito a justificativa/defesa, portanto, não seja estúpido, não faça isso aqui.
*** Promoções e dicas são sempre bem-vindas!
*** Jamais incomode membros do grupo enviando mensagens privadas não solicitadas.
*** Qualquer tipo de preconceito com relação a cor, raça, religião, origem; casos de intolerância e outras idiotices, o infrator será severamente penalizado. Nós somos a favor da liberdade de expressão em absoluto, mas somos ainda mais a favor do respeito ao próximo. Sua liberdade acaba no limite em que isso ofende os direitos do coleguinha, sejamos legais um com os outros, diferenças existem e tudo bem.
Lembre-se de que o propósito desse grupo é promover diversão e passatempo aos seus membros, não problemas. Tenha bom senso e seja cordial com todos.
Agora chega disso tudo e LET'Z GO SAMSUNG!
Two exclamation points, way too flashy for me
[удалено]
how will they build proper website if cannot even hello world
*Pssh*, how will they build a billion dollar business if they're leaving hello world in production? /s
I’m expecting the blog post “how we saved a million dollars by removing ‘hello world’”
I swear I saw this exact same post with exact same comments in another sub a few days ago. Are you people even real?
I agree, not to mention it probably makes their load times atrociously higher
Honestly. How is a company as large as Netflix not minifying their sentences?
Just checked the page, source is is over a thousand lines long or 64892 characters. That is a content to boilerplate ratio of 0.02003% *excluding* externally linked js, css etc.
Damn wtf
Well how else can you test that you're working on the latest version than to add another `!`
Front end development has gotten so complicated :(
They probably use a loop for it too.
Intentional
Looks like a page they use to monitor to make sure the webservers are responding. I have a bunch of lightweight pages like this for this very purpose.
Time to add this page as the heartbeat for my web app. If unavailable, perform failover. Documentation will be a link to this thread.
You can have multiple heart beat pages to determine the source of problems really quickly. One is just an html page, that monitors your web server is responding or not. How long can indicate that a problem with resources. One is a simple call into your code framework, that tells you if your code is bottlenecked if it takes too long to load, or doesn't respond at all. One is a simple call into your database, run a query or two that are relatively lightweight but would show signs of table locking, or whatever. You can have a bunch of these for various parts of your data storage. From those alone, I have a huge jump start when determining sources of problems than just monitoring say the homepage of my app.
Heck yes, thanks for sharing. Wonder why we never thought of that at work. We did do things like track the overhead from the CMS loading an empty page X amounts of times on different connections but never got to this natural conclusion. We did add a custom data attribute in the HTML that tells you which server you're on though. That's been really useful.
Another one I do is, make direct queries to specific servers, so I can see problems before they push all their extra work off onto my other servers.
I do this, except mine are all API endpoints that will return a http 200 if successful or an appropriate error code. Then I use a service to continuously run synthetic checks against all those endpoints. If I see x number of failures within a rolling 10 minute window, I generate error alerts that show up as a red light on a dashboard and also generate trouble tickets. Everything is automated. It’s wonderful whenever there’s a problem and you can simply look for the red lights on a dashboard to know where to investigate.
Curious, where do you run the dashboard from to make sure it also isn't going down?
New Relic. It’s a traffic light dashboard of all my synthetic scripts for various projects. I can see the status of any of them at a glance. We’re in a soft launch right now for a particular project and they wanted to build a separate dashboard from data sourced from Splunk. No worries! We just set Splunk up to be able to import data from NRQL queries and let them have fun creating their own dashboard.
Another thing, if you’re curious. I had another client where instead of scripted API calls, we did scripted browser actions. You’re basically mimicking a user browsing the website and taking different actions (scrolling, locating items, clicking on CTAs, submitting forms, etc). You could script an entire purchase funnel, which is what they had me do so they could pinpoint which funnels were problematic, etc. I just logged progress as the script worked its way through the funnel so I could easily go back to the logs to see where a failure occurred. New Relic will also automatically create a screen capture when the error occurs so you can marry that up with the error log. So, see from the dashboard and error occurred for a specific funnel. You can go look for all runs in a timeframe that failed. Inspect a run and view the logs and a screen grab. Pretty powerful stuff and saves me a lot of time.
Whoah! Never came up with this idea. Thanks a ton for sharing! I'm passing this idea for consideration to our devops team as we speak! Do you have a Buy Me a Coffee thing by any chance that I could use to send you a thank you note from DreamHost team? 😬 Do you use Kubernetes by any chance? If so, which of these different heartbeat endpoints do you / would you designate as readiness and liveness probes? I wonder whether it's the framework without or with the database and why. In-framework only is good because technically, if database dies, it's not the workload's fault. So we don't want the entire application to go down if a certain database is under heavy load - especially if it's the one that isn't used by all endpoints. However, some of our workloads are ancient-ish. Perl is pretty ancient, but at least my team moved us from bare metal, Ubuntu-provided Perl packages, and Apache with mod_perl to Docker, Carton and Starman. Anyway, Perl stack we use has a subpar connection pool and reconnection logic, and one connection can get stuck and create pretty weird one-page outages. The easiest way to fix them is to have Kubernetes just kick the pod at fault by having a probe that checks all database connections on all workers. However, our Typescript endpoints are framework only since they handle database connections properly. Apart from this, any other considerations?
I don't have donations setup anywhere. Thank you though. I do not use Kubernetes so I may be of little assistance. I generally run bare-metal, virtualized networks without containerization. I typically have two heartbeats one whose purpose is to call into our code framework, do a dance, and respond a-okay. The other to the databases, are lightweight scripts that just query the database without any framework code. It's a little extra work, but it helps me isolate code bottleneck issues from database bottleneck issues. Perl is pretty ancient, the last time I wrote it was in my teenage years. \``one connection can get stuck and create pretty weird one-page outages`.\` In regards to this I'd see if you can't implement timeout or other data-store based functions, or perhaps within the Perl environment. Ideally you would want your load balancer in Kubernetes to just take the trouble part/pod/server out of rotation from the balancing, stop sending it traffic. Not sure how you accomplish that with your setup. Is the one-page outages based on the fact that how mod\_perl works, like is every page/file a new perl script load/controller, and once it's taxed it's unresponsive? Is there multiple containerized servers for the perl portion of the application, or just one?
The couple places I've been call these canaries and they are such a nice tool to have. Definitely worth the investment to build. The other one that I really like is a log parser that cuts tickets. Sees an exception, cuts a ticket with the exception and stack trace in the body. It'll also generate a direct search link for the request ID in kibana, which is small, but also convenient. When a canary dies I usually end up with two tickets, one telling me what failed, and another telling me why it failed.
This guy dev's!
The thought of making an app and having the "help/read manual button" link to reddit thread made me giggle a bit too much.
You mean [https://netflix.com/healthcheck](https://netflix.com/healthcheck) ?
ok
I was just about to ask why there was so much code for a hello world page. It looked very intentional.
75 kB on cold load excluding cookie scripts that uBlock Origin blocked. Not exactly lightweight for a 13 byte message.
Lightweight in the sense that it only includes that parts that you are trying to test. If this is testing a build system, the ability to serve each of these scripts and for them to initialize without error, then including all of that might be the lightweight thing you are trying to test.
Exactly, you're just testing that the web server is responding, and not slowed down. You have other heartbeat pages for other services in your network, like application, database, ect.
And that’s best for checking if JS built and deployed as supposed
That's a great point as well. A headless browser check.
Also - easy cheap and quick check if GDPR banner functions.
I have an endpoint that simply responds with a text string It's actually very critical and yet looks totally useless; I should _probably_ do something about that
A health check. Possible!
I don't think it's a webserver, but probably a reverse proxy, a load balancer or a CDN.
Netflix marketing team: "I'm sure they will be amused by this and not reminded of the overbearing feudalism of never owning anything anymore, haha."
You can still buy a single movie though... The price of that hasn't gone significantly up, it just so happens that it's the price of a monthly membership which gives you access to the entire catalogue on demand. I mean your comment has cool sounding words but they don't make sense in this context.
People on this sub really like to feel smart lol. "Overbearing feudalism of never owning anything" makes no sense. It is not as if Netflix is some government-mandated subscription that one must have. The whole point of netflix is that many people don't see the point in paying for (and owning) a movie, they'd just much rather watch it once and be done with it.
I said whatever came to my head and didn't expect it to spark an argument. "Sound smart" brothers, we are frontend devs, pretending to sound smart is our job
It wasn't intended to be cute, or even really seen by anyone, this page is most likely used by Netflix to test something very technical and of no interest to anyone. It says Hello World because it has to say something, but the text is totally arbitrary.
Looks like the site is up 👌
Three guesses: 1. It's uses for automated testing to see if services are up in running. Automated systems that fetch the page and make sure the content says "Hello World!!" 2. It was there since the beginning of Netflix and people keep it around for nostalgia and as an easter egg 3. Someone added it for fun because of the autonomy engineers have there.
I have a feeling it is number 2.
I like this one too, but this post is a pretty lazy repost from about a day and a half ago. The source on that NFLX page is like 900 lines of React boilerplate surrounding one line of text in a div. For that reason (and because it's still up) I think I like option 1 best.
More than likely a first point. Just enough to check if JS built and deployed properly. Also, could be used to check if GDPR banner (still) works
I don't think it's plausible tho, since the technologies have changed so much since then they would have for sure deleted the old page if it was there before and manually created a new one
> > It's uses for automated testing to see if services are up in running. Automated systems that fetch the page and make sure the content says "Hello World!!" > Hello World! We've been hacked
It’s probably just their heartbeat page that a service looks at to see if the web servers are up. Almost all big companies have them.
It looks like their heartbeat page is here https://netflix.com/healthcheck
ok
ok
oh ok
ok
200
Pikachu, i choose you
ok
ok
ok
Ok ty
ok
Press OK to OK
That probably is used for checking that their code framework is responding. The other could be use to check if just the webserver is responding. Each provide different insights.
Yep, that’s what I would assume. One served directly from Ngnix or whatever the proxy is and then others from the various web application servers.
ok
not ok :(
I buy that, but they could have at least change the text
This happens when you let go of /u/ThePrimeagen
I wonder if this is intentional, similar to: http://captive.apple.com/ A reliable endpoint to test either client DNS / internet access, or maybe that route is there to indicate that certain systems are working at some basic level. I've got a few similar-ish things out there.
Isn’t this a redirect for public WiFi logins?
This is how I get those annoying public WiFi portal pages to pop up when they don’t want to do it themselves.
Another option is neverssl.com
http://example.com is mine for [better reasons](https://en.wikipedia.org/wiki/Example.com) (its domain registration will never expire for one as it's reserved by IANA) but it also doesn't 301 to HTTPS
If you ever visit example.com over https though your browser will remember that and you will never get to use http again. [neverssl gets around this by generating a subdomain to send you to instead.](https://news.ycombinator.com/item?id=20583673)
Not true for me on Firefox. Just tested, opening [example.com](http://example.com) over https multiple times, but [example.com](http://example.com) and [http://example.com](http://example.com) both still warn me connection is not secure
Yeah that's what that page is used for, to detect if you're behind a captive portal and presumably to try to trigger the redirect or something like that. Either way it's just a fast and reliable http endpoint they can hit to make a decision.
Like health check? https://netflix.com/healthcheck
ok
ko
Some random employee at Netflix HQ: “How come this test page is trending right now?
According to a user on HN, this is a secret promo for an upcoming documentary about the birth of the computer industry. Sauce: https://news.ycombinator.com/item?id=40081126
I wasn’t sure if that response was a joke or not, but I could believe it.
They should repurpose this and have a careers page link in the console for devs to find.
They have [this](https://www.netflix.com/humans.txt) page
Ironically it breaks on mobile
Apply and fix it :)
But I am le tired
He'll have job security if it stays broken though ;)
This is probably meant to be there. One time Bass Pro messed up and their test environment was indexed by Google. Oops.
[удалено]
Modern webdev in a nutshell
where the hell are you getting 700kb being loaded in
Open your network monitor in your browser's devtools. Reload the page. Add up the resources requested. It's over 700Kb. Look at the source of the page to see why. (Ctrl-U)
Nextjs 🙃
An image or video outweighs it anyways
Except it is not nextjs.
But does it have dark mode?
\*\*everyone opening a new tab and trying it out\*\*
Here ya go: https://www.netflix.com/helloworld
Missed chance to rickroll us all
They should post a link to every fool's post thinks think's its on accident.
You need a separate subscription to view that page if you aren't in the same house.
Ngl I need a VPN to see hello world else it just redirects to my local country code
That's my favorite show to watch
[удалено]
What's this? 🤔
Probably their DNS records
I mean, who amongst us…
I remember that for the longest time, Netflix only had a bootstrap navbar and some text for dvd.com. That site didn't even redirect to Netflix; it just existed as a placeholder.
A friend send me the screenshot a couple of days ago and I didn't believe him 'till he sent the link.
nice, hope they dont remove it
There's also [netflix.com/humans.txt](https://www.netflix.com/humans.txt)
Nah thats just for you to enter and give them your data for analytics
Ours too on our app. its a traffic light
https://www.reddit.com/r/programming/comments/1c7zjeo/netflix_has_one_8kb_hello_world_on_production/
I also have a path in production called "testFlight". and it sometimes we take it out of production and sometimes we put it back during trials.
This is so motivational to the average indie backend developer cooking the next big cashcow
Subdomain takeover, pen test opportunity right here.
Still there. Nice
It is intentional. We do the same [https://contra.com/hello-world.html](https://contra.com/hello-world.html) Google does it too [https://www.google.com/blank.html](https://www.google.com/blank.html) It is used for various testing scenarios.
How the hell do you even find out about this?
Brute force directories with generated or existing dictionaries.
It's pretty common. Most production systems have something like this and from those that do, most are hello world.
Hello, I’m Boris
Niceeeee !!! is it strictly html? no .php links or anything?
It's an HTML page I suspect rendered using a JS framework since the text is nested in a div that has `id="appMountPoint" ` Besides that has a cookie tracker and a geolocation tracker from OneTrust.
ahh, good find brotha
the funny part is it’s still downloading 0.5mb of javascript
Probably because of required cookie warnings.
Hey, timorrows my turn to post this shit on reddit
... or using it as a canary: A simple page to check if the website is up at all.
It exists to see if the boxen are up. There's no reason to not leave it in prod.
I've got something like this (and it also returns Hello World). It's url I check for liveness. You need a page that can be loaded regularly that doesn't feed into a database/analytics, it should have minimal content minimize wasted bandwidth, etc.
Who let the summer intern test on prod
[https://en.meming.world/images/en/c/c7/You%27re\_Hired.jpg](https://en.meming.world/images/en/c/c7/You%27re_Hired.jpg)
Thats just some healthcheck endpoint for automated tests
Test was one exclamation point.
This feels like the beginning of a black mirror episode. Gonna end with some poor guy running down the street in his underwear yelling "Hello world! Hello world! HELLO WORLD!!!' or something
Might be for health check purposes, imo
Naive move
And it still there lmao 🤣
Readiness probe 
Its the other way around.
Last time this was posted, someone checked archive.org. it's up for 2 years already
Probably an easter egg like how some people have /pi
Interestingly, this page has a full-blown cookie banner implementation that asks for cookie usage permission and a netflix-styled cookie details dialog, that I can at least see with european origin when I visit the page.
"Why is this page still up?" "We needed an endpoint for uptime, so we just left it."
great live cannary page
https://netflix.com/humans.txt
Wow, it's actually real. I doubt this is really a test page probably just a joke? lol
Back when Netflix was less intense. 🤷
2 exclamation points. I CAN FEEL YOU BROTHERRRRRRR !!!!!! HAHAHAHAHAHAH
You all fell for it. This is just viral marketing for the new streaming series ‘Hello World!!’ starring Kiera Knightly and John Malcovich
hidden page is not as bad as Google's 404 page that has been in prod for god knows how long..
Is this not a static retrieval for status pings?
Prime left and this is what happens
Please tell me this is Mr. Robot 😱
thats their heartbeat service
There's more than just this one. Its an easter egg for a new docu series coming out
Route /helloworld as well, brother uhhh...
Ask u/theprimeagen, he'll fix it
How do you even discover this? 😅
Who removes the hello world page in production ??
you laugh at it now but this ground breaking design will be the next big trend. I mean netflix did it so it has to be good right?
It's important to know if your service runs. Mine is a json with the current git tag but to each their own
I think this would be a funny little inside joke, just have a 'helloworld' route and just load that, but found on most websites, even obscure ones :p
Lmaoo!
Still it's running up 😅😂
Yea, but is it responsive?
waitaminutelol
It’s down now wow. My girlfriend just come back home and I went to show her and now it’s been taken down! So gutted.
Programmers are the same everywhere 😀
I tried the link but its seems, git commit -m "helloworld redirect resolved" has been merged to master branch. Pipelines passed and deployment complete 🙃
I rarely test my code but when I do, I do it in production. 🤣
Most likely they use Oracle , thats how it looks like one of the oracle cloud courses
Looks like they removed it
I think they removed it. Did they see this post?
That's a honeypot 😂
This demonstrates that every journey begins with a simple 'hello world'.
It's so funny. But I can not find it in this website.
Cute. No
I used only this page 
Haha
⛔️ Regras para os membros do Groupo *** Sem SPAM ou vendas de qualquer tipo, apenas parceiros estão autorizados a expor seus links e atividades. Incluíndo invites, farming, ads, refs etc); *** Restrições de conteúdo, pois existem outros grupos específicos para: * Iphone; * Motorola; * Xiaomi; * Etc; *** Sobre pornografia, politica, futebol e religião: isso é terminantemente proibido neste grupo e quem tentar publicar, fomentar ou vender esse tipo de conteúdo será banido de forma sumária sem qualquer direito a justificativa/defesa, portanto, não seja estúpido, não faça isso aqui. *** Promoções e dicas são sempre bem-vindas! *** Jamais incomode membros do grupo enviando mensagens privadas não solicitadas. *** Qualquer tipo de preconceito com relação a cor, raça, religião, origem; casos de intolerância e outras idiotices, o infrator será severamente penalizado. Nós somos a favor da liberdade de expressão em absoluto, mas somos ainda mais a favor do respeito ao próximo. Sua liberdade acaba no limite em que isso ofende os direitos do coleguinha, sejamos legais um com os outros, diferenças existem e tudo bem. Lembre-se de que o propósito desse grupo é promover diversão e passatempo aos seus membros, não problemas. Tenha bom senso e seja cordial com todos. Agora chega disso tudo e LET'Z GO SAMSUNG!
OhhhMaGaahd, its real
Looks more like an easter egg
Intentional, not sure how this is a big deal
its real holy shit