"insecure http connection"를 이탈리아 사람로 번역

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 Some pages on your site may have mixed content, meaning the page loads over a secure HTTPS connection, but some content loads over an insecure HTTP connection

• mixed content
• meaning the page
• secure HTTPS connection
• insecure HTTP connection

EN Some pages on your site may have mixed content, meaning the page loads over a secure HTTPS connection, but some content loads over an insecure HTTP connection

• mixed content
• meaning the page
• secure HTTPS connection
• insecure HTTP connection

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 However, you can choose the Insecure setting so visitors can still use the HTTP version, even with SSL enabled.

• However
• choose the Insecure
• visitors can still
• HTTP version
• even with SSL

EN However, you can choose the Insecure setting so visitors can still use the HTTP version, even with SSL enabled.

• However
• choose the Insecure
• visitors can still
• HTTP version
• even with SSL

EN HSTS tells all modern browsers to connect to our servers over a secure connection only, even if you try to access an insecure page via bookmark, link or URL.

• browsers to connect
• access an insecure
• via bookmark
• link

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 For an overview of the most used browsers, visit the site: http://www.cookiepedia.co.uk/index.php?title=How_to_Manage_Cookies or the site http://www.aboutcookies.org/ and http://www.youronlinechoices.eu/

• used browsers
• visit the site
• site

EN Also, HTTPS is currently a requirement to capitalize on higher performing protocols such as HTTP/2 and HTTP/3 (also known as HTTP over QUIC)

• HTTPS is currently
• requirement to capitalize
• higher performing protocols
• HTTP
• known as HTTP
• QUIC

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 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 It is also worth noting that if a site is in HTTP/2 and establishes a connection to a resource that is still in HTTP 1.1, they will simply communicate in the previous language.

• establishes a connection
• HTTP
• previous

EN It is also worth noting that if a site is in HTTP/2 and establishes a connection to a resource that is still in HTTP 1.1, they will simply communicate in the previous language.

• establishes a connection
• HTTP
• previous

EN In HTTP/1.1, the six connections a browser could open to a domain can over time claim six times as much bandwidth as a single HTTP/2 connection

• HTTP
• claim six times
• single HTTP
• connection

EN Since both HTTP/2 and HTTP/1.1 can be served from the same TCP port (443), browsers don?t need to make this selection before opening a connection.

• Since both HTTP
• HTTP
• TCP port
• browsers don
• selection before opening

EN These fast connection setup times are expected to really help HTTP/3 outperform HTTP/2.

• fast connection setup
• expected to really
• HTTP
• outperform HTTP

EN HTTP/3 and QUIC are highly advanced protocols with powerful performance and security features, such as a new HTTP prioritization system, HOL blocking removal, and 0-RTT connection establishment

• HTTP
• QUIC are highly
• protocols with powerful
• security features
• HTTP prioritization system
• HOL blocking removal
• connection establishment

EN A cookie with the "Secure" attribute is sent to the server only through a secure HTTPS connection, not through any unsecured HTTP connection.

• attribute is sent
• secure HTTPS connection
• unsecured HTTP

EN A cookie with the "Secure" attribute is sent to the server only through a secure HTTPS connection, not through any unsecured HTTP connection.

• attribute is sent
• secure HTTPS connection
• unsecured HTTP

EN In 1997, HTTP/1.1 was introduced to allow TCP connection reuse by adding ?keep-alives?, aimed at reducing the total cost of connection start-ups

• HTTP
• introduced to allow
• keep-alives
• aimed at reducing
• start-ups

EN A big success has been the decrease in website connection usage due to HTTP/2 connection multiplexing

• decrease in website
• connection multiplexing

EN The Kill Switch feature built into the app controls your connection to the VPN server. If the connection is lost, Kill Switch blocks your device's Internet connection to avoid data leakage.

• Kill Switch feature
• VPN server
• connection is lost
• Kill Switch blocks
• device's Internet connection

EN Automatic HTTPS Rewrites safely eliminates mixed content issues while enhancing performance and security by rewriting insecure URLs dynamically from known (secure) hosts to their secure counterpart

• Automatic HTTPS Rewrites
• eliminates mixed content
• while enhancing performance
• security by rewriting
• secure
• counterpart

EN Insecure communication between devices and the backend

• Insecure communication between
• backend

EN A seamless user experience leads to fewer vulnerabilities, because no one’s tempted to store secrets in an insecure config file.

• seamless user experience
• fewer vulnerabilities
• tempted to store
• insecure config

EN Similar to HTTPS, DNSSEC adds a layer of security by enabling authenticated answers on top of an otherwise insecure protocol

• Similar to HTTPS
• security by enabling
• answers on top
• otherwise insecure protocol

EN Without compromising data security with insecure public cloud providers

• insecure public cloud

EN Is app data insecure, and will app platforms eventually hide it?

• app data insecure
• app platforms eventually

EN No, there is nothing inherently insecure about app data

• nothing inherently insecure

EN Some special situations might need the Insecure option

• special situations might
• Insecure option

EN If your site has a lot of custom code or third-party embeds, you may want to check Insecure

• custom code
• third-party embeds
• want to check

EN Domains registered or connected before October 2016 are set to Insecure.

• Domains registered
• connected before October

EN If you check Insecure, ensure the domain’s SSL certificate is valid.

• check Insecure

EN Note: Disabling HSTS or switching to the Insecure setting can temporarily prevent access to your site

• Note
• Disabling HSTS
• setting can temporarily

EN The checkout page is always secure, even if your site is using the Insecure SSL setting.

• secure
• Insecure SSL

EN Insecure content can come from:

EN The large amount of information we receive every day and the endless choices open to us quite often leave us insecure and confused

• receive every day
• endless choices open
• quite often leave
• insecure
• confused

EN • CWE-522: Insufficiently Protected Credentials: The product transmits or stores authentication credentials, but it uses an insecure method that is susceptible to unauthorized interception and/or retrieval.

• Insufficiently Protected Credentials
• product transmits
• stores authentication credentials
• uses an insecure
• susceptible to unauthorized

EN Insecure: Improper configurations can allow intruders and malicious actors to gain access to computers in your home. Furthermore, exposing your home IP address can be a security risk.

• Insecure
• intruders
• access to computers
• home
• Furthermore
• exposing your home
• security

EN The default values for this are very insecure, so be sure to change the password at the very least

• very insecure
• sure to change
• least

EN Insecure logins, confusing group features, hard to add / manage new devices? Those issues are a thing of the past with our improved Add a New Device page

• Insecure logins
• confusing group features
• hard to add
• manage new devices
• Device page