4 ms·

Hah! I appreciate your reply :)

• dylan604 3y ago
  The question I’m really wondering from your post is why is a server being hugged to death able to respond to a curl request and not a browser’s request?
  • esquivalience 3y ago
    Presumably this was just downloading the source file, not the linked images and any other heavier aspects of the page.
  • lucb1e 3y ago
    If there's enough threads on the web server being blocked by waiting for WordPress (99% of the websites that HN hugs to death are WP), then once the HTML has loaded (which, in curl, would mean the loading is complete) you are still waiting for threads to serve you the css, images, and scripts. I think in total, the curl loading time was about half of the in-browser page. Both loaded in the end, I just happened to be more patient with curl because I know the server is busy and it's not just a stupid javascript dependency that I'm waiting on.
    • dylan604 3y ago
      ah, for some reason I assumed (yeah, I know), that the curl request responded quickly. understanding that the curl request was also delayed now makes much more sense. i get that curl only downloads the HTML and not the other included links, that part was obvious.