This specification describes an optimized expression of the semantics of the Hypertext Transfer Protocol (HTTP), referred to as HTTP version 2 (HTTP/2). HTTP/2 enables a more efficient use of network resources and a reduced perception of latency by introducing header field compression and allowing multiple concurrent exchanges on the same connection. It also introduces unsolicited push of representations from servers to clients. This specification is an alternative to, but does not obsolete, the HTTP/1.1 message syntax. HTTP's existing semantics remain unchanged.
HTTP headers are an important way of controlling how caches and browsers process your web content. But many are used incorrectly or pointlessly, which adds overhead at a critical time in the loading of your page, and may not work as you intended.
User agents commonly apply same-origin restrictions to network requests. These restrictions prevent a client-side Web application running from one origin from obtaining data retrieved from another origin, and also limit unsafe HTTP requests that can be automatically launched toward destinations that differ from the running application's origin. In user agents that follow this pattern, network requests typically include user credentials with cross-origin requests, including HTTP authentication and cookie information.
Cross-Origin Resource Sharing (CORS) is a specification that enables truly open access across domain-boundaries. If you serve public content, please consider using CORS to open it up for universal JavaScript/browser access.
Let’s start with an example. Say we have an amazing website with a login to protect some private data we made available to our users at /private. We won’t make this example too complicated, so let’s…
HTTP/2 is poised to eliminate much of the waste that developers deal with. Multiplexed connections will eliminate the need to bundle JavaScript libraries together. But is HTTP/2 a panacea to all our problems? What about WebSocket? Allan Denis tells us what HTTP/2 is good at and debunks some myths about what it can do.
OAuth 2 is an authorization framework that enables applications to obtain limited access to user accounts on an HTTP service, such as Facebook, GitHub, and DigitalOcean. It works by delegating user authentication to the service that hosts the user acc
Read on to learn the basics of OAuth 2.0, key terms, registering clients and getting client credentials, etc., as well as to learn how to get access tokens.
The Service Oriented Architecture (SOA) introduced a design paradigm, which talks about a highly decoupled service deployment where the services talk to each other over the network with a…
RxJS is the best library out there to handle data streams and use different filters to transform data, while Axios is the one of the best libraries out there to handle cross-browser Ajax requests. If…