Table of contents
HTTP
is an application protocol for distributed, collaborative, and hypermedia information systems.
As HTTP is an open source project, you can find more
open source alternatives and stats
on LibHunt.
Simplicity
HTTP is a simple protocol that is easy to understand and implement, making it accessible for developers and widely adopted across the web.
Statelessness
HTTP is stateless, meaning each request from a client to server is independent, which simplifies server design and allows for easier scaling.
Flexibility
HTTP is designed to transport different types of data and supports a variety of methods (GET, POST, PUT, DELETE, etc.), making it flexible for various applications.
Extensibility
HTTP supports extensions and new methods, headers, and functionalities can be added without breaking existing implementations.
Cacheability
HTTP supports caching which can reduce latency and network congestion and improve efficiency by storing copies of resources closer to the client.
We have collected here some useful links to help you find out if HTTP is good.
Check the traffic stats of HTTP on SimilarWeb. The key metrics to look for are: monthly visits, average visit duration, pages per visit, and traffic by country. Moreoever, check the traffic sources. For example "Direct" traffic is a good sign.
Check the "Domain Rating" of HTTP on Ahrefs. The domain rating is a measure of the strength of a website's backlink profile on a scale from 0 to 100. It shows the strength of HTTP's backlink profile compared to the other websites. In most cases a domain rating of 60+ is considered good and 70+ is considered very good.
Check the "Domain Authority" of HTTP on MOZ. A website's domain authority (DA) is a search engine ranking score that predicts how well a website will rank on search engine result pages (SERPs). It is based on a 100-point logarithmic scale, with higher scores corresponding to a greater likelihood of ranking. This is another useful metric to check if a website is good.
The latest comments about HTTP on Reddit. This can help you find out how popualr the product is and what people think about it.
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 / about 1 year ago
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 / about 2 years ago
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 3 years ago
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: almost 4 years ago
The program you are using to send data to the server may or may not automatically determine the right content-type header for your data, and knowing how to set and check headers is an essential skill. To learn more about the HTTP protocol check out the MDN guide or read the official standard, RFC 7230. - Source: dev.to / about 4 years ago
It's neat, but I don't believe it is a compliant implementation of HTTP/1.1 (or 1.0). For example, it does not handle percent-encoded characters in the request URI.[1][2] [1]: https://datatracker.ietf.org/doc/html/rfc7230#section-3.1.1 [2]: https://www.w3.org/Protocols/HTTP/1.0/spec.html#Request-URI. - Source: Hacker News / about 4 years ago
This is wrong. HTTP/1.0 had a keep-alive header field as mentioned in the HTTP/1.1 RFC: https://tools.ietf.org/html/rfc7230#appendix-A.1.2 But in HTTP/1.1 that's the default: https://tools.ietf.org/html/rfc7230#section-6.3- Source: Hacker News / over 4 years agoo If the received protocol is HTTP/1.1 (or later), the connection will persist after the current response; else,.
Context: RFC 2616 and RFC 7230 require CRLF line endings instead of just LF. 1. https://tools.ietf.org/html/rfc2616 2. https://tools.ietf.org/html/rfc7230. - Source: Hacker News / over 4 years ago
Do you know an article comparing HTTP to other products?
Suggest a link to a post with product alternatives.
Is HTTP good? This is an informative page that will help you find out. Moreover, you can review and discuss HTTP here. The primary details have not been verified within the last quarter, and they might be outdated. If you think we are missing something, please use the means on this page to comment or suggest changes. All reviews and comments are highly encouranged and appreciated as they help everyone in the community to make an informed choice. Please always be kind and objective when evaluating a product and sharing your opinion.
