Traduzir "making http requests" para holandês

EN More importantly, since HTTP/3 uses QUIC (hence UDP) where prior versions of HTTP use TCP, HTTP/3 will always be at a different endpoint from the HTTP/1.x and HTTP/2 service.

• importantly
• since HTTP
• uses QUIC
• hence UDP
• TCP
• HTTP

EN Last year?s analysis of HTTP Archive data showed that HTTP/2 was used for over 50% of requests and, as can be seen, linear growth has continued in 2020; now in excess of 60% of requests are served over HTTP/2.

• Last year
• analysis of HTTP
• showed that HTTP
• requests
• seen
• served over HTTP

EN When comparing Figure 22.3 with last year?s results, there has been a 10% increase in HTTP/2 requests and a corresponding 10% decrease in HTTP/1.x requests. This is the first year that gQUIC can be seen in the dataset.

• year
• results
• increase in HTTP
• requests
• year that gQUIC

EN Less than 7% of sites make no HTTP/2 or gQUIC requests, while (only) 10% of sites are entirely HTTP/2 or gQUIC requests.

• HTTP
• gQUIC requests
• while
• sites are entirely
• gQUIC

EN A line chart comparing the fraction of first-party HTTP/2 requests with third-party HTTP/2 or gQUIC requests

• line chart comparing
• fraction of first-party
• requests with third-party
• gQUIC requests

EN Figure 22.7 orders every website by the fraction of HTTP/2 requests for known third parties or first party requests compared to other requests

• Figure orders every
• fraction of HTTP
• requests for known
• parties
• party requests compared
• requests

EN The median mobile website has 24 third-party requests (23 on desktop) and it increases exponentially from 2 requests for both at the 10th percentile to 104 requests on mobile and 106 requests on desktop at the 90th percentile.

• median mobile website
• third-party requests
• desktop
• requests on mobile
• requests on desktop

EN HTTP: This will route from HTTP, usually to the same HTTP. If used with HTTPS on the right side, it may cause errors to occur.

• HTTP
• route from HTTP
• used with HTTPS
• right side

EN HTTP Secure (HTTPS) is the safe version of the Hypertext Transfer Protocol (HTTP) for secure online transactions. It is easy to see the difference because with the protocol HTTP, URLs start with

• HTTP Secure
• HTTPS
• Hypertext Transfer Protocol
• HTTP
• secure online transactions
• protocol HTTP

EN HTTP: This will route from HTTP, usually to the same HTTP. If used with HTTPS on the right side, it may cause errors to occur.

• HTTP
• route from HTTP
• used with HTTPS
• right side

EN HTTP Secure (HTTPS) is the safe version of the Hypertext Transfer Protocol (HTTP) for secure online transactions. It is easy to see the difference because with the protocol HTTP, URLs start with

• HTTP Secure
• HTTPS
• Hypertext Transfer Protocol
• HTTP
• secure online transactions
• protocol HTTP

EN HTTP/3 is the latest version of HTTP, and it builds upon the success of HTTP/2 by adding several new features and improvements

• HTTP
• improvements

EN As the HTTP protocol has evolved, the semantics of HTTP have stayed the same; there have been no changes to the HTTP methods (such as GET or POST), status codes (200, or the dreaded 404), URIs, or header fields

• semantics of HTTP
• stayed the same
• methods
• POST
• status codes
• dreaded
• URIs
• header fields

EN Is there any difference in which content-types are served over HTTP/2 or gQUIC? Figure 22.8 shows, for example, that 90% of websites serve 100% of third party fonts and audio over HTTP/2 or gQUIC, only 5% over HTTP/1.1 and 5% are a mix

• served over HTTP
• gQUIC
• Figure shows
• example
• party fonts
• audio over HTTP
• HTTP
• mix

EN As discussed in the HTTP/1.0 to HTTP/2 section, HTTP/2 multiplexes multiple different streams on top of one connection

• HTTP
• section
• multiplexes multiple different

EN Since QUIC and HTTP/3 run over UDP, things aren?t as simple as with HTTP/1.1 or HTTP/2

• Since QUIC
• HTTP
• run over UDP
• things aren

EN This likely will have to be done for each domain separately, which will probably lead to most page loads using a mix of HTTP/1.1, HTTP/2, and HTTP/3.

• done for each
• separately
• mix of HTTP
• HTTP

EN Most likely, we will continue to see a healthy mix of HTTP/3, HTTP/2, and even HTTP/1.1 on the web for years to come.

• likely
• HTTP
• even HTTP
• web for years

EN Home pages have seen a 13% increase in HTTP/2 adoption, leading to an even split of pages served over HTTP/1.1 and HTTP/2

• increase in HTTP
• adoption
• split of pages
• HTTP

EN Highlight plain http requests to the HTTP API as insecure.

• Highlight plain http

EN HTTP headers are the core part of requests and responses in the Hypertext Transfer Protocol (HTTP)

• Transfer Protocol
• HTTP

EN This is reflected by the usage numbers in the HTTP Archive data, where no HTTP/3 requests were identified at all

• HTTP
• requests were identified

EN HTTP API requests, with response code, responsible component, and time taken, with alerts for failed or erroneous requests.

• HTTP API requests
• response code
• responsible component
• taken
• alerts for failed
• erroneous

EN HTTP API requests, with response code, responsible component, and time taken, with alerts for failed or erroneous requests.

• HTTP API requests
• response code
• responsible component
• taken
• alerts for failed
• erroneous

EN HTTP API requests, with response code, responsible component, and time taken, with alerts for failed or erroneous requests.

• HTTP API requests
• response code
• responsible component
• taken
• alerts for failed
• erroneous

EN HTTP API requests, with response code, responsible component, and time taken, with alerts for failed or erroneous requests.

• HTTP API requests
• response code
• responsible component
• taken
• alerts for failed
• erroneous

EN HTTP API requests, with response code, responsible component, and time taken, with alerts for failed or erroneous requests.

• HTTP API requests
• response code
• responsible component
• taken
• alerts for failed
• erroneous

EN HTTP API requests, with response code, responsible component, and time taken, with alerts for failed or erroneous requests.

• HTTP API requests
• response code
• responsible component
• taken
• alerts for failed
• erroneous

EN HTTP API requests, with response code, responsible component, and time taken, with alerts for failed or erroneous requests.

• HTTP API requests
• response code
• responsible component
• taken
• alerts for failed
• erroneous

EN HTTP API requests, with response code, responsible component, and time taken, with alerts for failed or erroneous requests.

• HTTP API requests
• response code
• responsible component
• taken
• alerts for failed
• erroneous

EN HTTP API requests, with response code, responsible component, and time taken, with alerts for failed or erroneous requests.

• HTTP API requests
• response code
• responsible component
• taken
• alerts for failed
• erroneous

EN HTTP API requests, with response code, responsible component, and time taken, with alerts for failed or erroneous requests.

• HTTP API requests
• response code
• responsible component
• taken
• alerts for failed
• erroneous

EN HTTP API requests, with response code, responsible component, and time taken, with alerts for failed or erroneous requests.

• HTTP API requests
• response code
• responsible component
• taken
• alerts for failed
• erroneous

EN HTTP API requests, with response code, responsible component, and time taken, with alerts for failed or erroneous requests.

• HTTP API requests
• response code
• responsible component
• taken
• alerts for failed
• erroneous

EN HTTP API requests, with response code, responsible component, and time taken, with alerts for failed or erroneous requests.

• HTTP API requests
• response code
• responsible component
• taken
• alerts for failed
• erroneous

EN HTTP API requests, with response code, responsible component, and time taken, with alerts for failed or erroneous requests.

• HTTP API requests
• response code
• responsible component
• taken
• alerts for failed
• erroneous

EN HTTP API requests, with response code, responsible component, and time taken, with alerts for failed or erroneous requests.

• HTTP API requests
• response code
• responsible component
• taken
• alerts for failed
• erroneous

EN HTTP API requests, with response code, responsible component, and time taken, with alerts for failed or erroneous requests.

• HTTP API requests
• response code
• responsible component
• taken
• alerts for failed
• erroneous

EN HTTP API requests, with response code, responsible component, and time taken, with alerts for failed or erroneous requests.

• HTTP API requests
• response code
• responsible component
• taken
• alerts for failed
• erroneous

EN HTTP API requests, with response code, responsible component, and time taken, with alerts for failed or erroneous requests.

• HTTP API requests
• response code
• responsible component
• taken
• alerts for failed
• erroneous

EN HTTP API requests, with response code, responsible component, and time taken, with alerts for failed or erroneous requests.

• HTTP API requests
• response code
• responsible component
• taken
• alerts for failed
• erroneous

EN HTTP API requests, with response code, responsible component, and time taken, with alerts for failed or erroneous requests.

• HTTP API requests
• response code
• responsible component
• taken
• alerts for failed
• erroneous

EN QUIC is dependent on TLS 1.3, which is used for around 41% of requests, as shown in Figure 22.21. That leaves 59% of requests that will need to update their TLS stack to support HTTP/3.

• QUIC is dependent
• TLS
• used for around
• requests
• shown in Figure
• leaves of requests
• update their TLS
• HTTP

EN Bar chart showing the distribution of requests per page. Desktop pages tend to load more requests. The 10, 25, 50, 75, and 90th percentiles for mobile pages are: 23, 42, 70, 114, and 174 requests per page.

• Bar chart showing
• distribution of requests
• page
• Desktop pages tend
• load more requests
• percentiles for mobile
• requests per

EN However, HTTP/3 over QUIC is already peeking around the corner! Over four years in the making, this next version of HTTP is almost standardized at the IETF (expected in the first half of 2021)

• However
• HTTP
• QUIC is already
• around the corner
• making
• IETF

EN When making HTTP requests for pages over the Internet, a browser sends a number of information header lines to the web server which will serve that request

• making HTTP requests
• serve that request

EN When making HTTP requests for pages over the Internet, a browser sends a number of information header lines to the web server which will serve that request

• making HTTP requests
• serve that request

EN Whenever a redirect occurs, Query Monitor adds an HTTP header containing the call stack, so you can use your favourite HTTP inspector or browser developer tools to trace what triggered the redirect.

• Whenever a redirect
• Query Monitor adds
• HTTP header containing
• call stack
• favourite HTTP inspector
• browser developer tools
• trace what triggered

EN HTTP Response Codes (only available on HTTP and HTTPS Monitor Types)

• HTTP Response Codes
• available on HTTP
• HTTPS Monitor Types

EN Set 301 redirects between http:// and the http://www versions of your domain. This is something we often forget, but it’s a must in SEO.

• Set redirects between
• domain
• something we often