HTTP Reviews

Arc Reviews

HTTP mentions (9)

• The History of HTTP

  HTTP/1.1 was first published as RFC 2068 (The Proposed Standard) in January 1997. HTTP/1.1 protocol was refined over two revisions, RFC 2616 published in June 1999 and RFC 7230-RFC 7235 published in June 2014 before the release of HTTP/2. The HTTP/1.1 standard (RFC 2616) remained stable for over 15 years. In 2022, HTTP/1.1 was updated again with RFC 9110 & RFC 9112. - Source: dev.to / 9 months ago

• State management in Svelte apps

  HTTP was invented as a stateless protocol, which means that each request fully encapsulates all of the information necessary to return a correct response. So historically, web pages never had to worry about managing state - each request to a URL with parameters or with a form submission would receive a response with all of the HTML that the browser needed to render content. - Source: dev.to / almost 2 years ago

• Evolving the Web: Discovering the History of HTTP Versions

  HTTP/1.1 was such a game changer for the Internet that it works so well that even through two revisions, RFC 2616 published in June 1999 and RFC 7230– RFC 7235 published in June 2014, HTTP/1.1 was extremely stable until the release of HTTP/2.0 in 2014 — Nearly 18 years later. Before continuing to the next section about HTTP/2.0, let us revisit what journey HTTP/1.1 has been through. - Source: dev.to / almost 3 years ago

• Poll: Are client web requests sent to upstream servers or downstream servers?

  On the one hand, it just seems natural that "upstream" refers to the inbound request being sent from one system to another. It takes effort (connection pooling, throttling, retries, etc.) to make a request to an (upstream) dependency, just as it takes effort to swim upstream. The response is (usually) easy... Just return it... hence, "downstream". Recall the usual meaning of "upload" and "download". Upstream seems... - Source: Hacker News / over 4 years ago

• How to cache TCP, SSL handshake on ALB?

  To me it sounds like you’ve not solved this as the config you’ve mentioned is about preventing “illegal” (none RFC7230 ) requests, it isn’t really related to the problem you posted. Source: over 4 years ago

Arc mentions (77)

• Nook Browser

  Because both are trying to be response to the death of Browser Company's Arc. (https://arc.net). - Source: Hacker News / 8 months ago

• I tried 6 next-gen browsers - here's what I found

  Arc was first recommended to me by a fellow dev. It felt like the browser I was looking for but never quite found. The Browser Company released this trendsetter in 2023, and among the frontend and tech community it quickly became the new shiny browser. I joined the trend in December 2023, and Arc became my default browser for more than a year. The browser focuses on user experience and brings minimal but modern... - Source: dev.to / 8 months ago

• Arc vs. Dia: A Developer’s Take on Two Browsers from The Browser Company (Plus: How to Get Access to Both)

  Arc was first recommended to me by a fellow developer, and it immediately felt like the browser I’d always wanted but never quite found. I’m a sucker for clean interfaces, and as both a frontend developer and a designer, I notice the details - beautiful UI, intuitive flows, and features that actually solve daily annoyances. - Source: dev.to / about 1 year ago

• My Recommended Zen Mods Plugins (Bite-size Article)

  In a previous article, I mentioned that unlike Arc Browser, Zen does not allow pinned tabs to be organized into folders (at this point), which I found inconvenient. While this plugin doesn't directly solve that issue, it does help organize pinned tabs neatly in a row, which I like. - Source: dev.to / over 1 year ago

• I tested Arc Browser

  Arc Browser is available on Windows, macOS and Linux (no, negative point). It's based on Chromium, so if you've already used Chrome, you won't feel out of place. Installing it couldn't be easier: go to the official website and download the version corresponding to your operating system. - Source: dev.to / over 1 year ago