From b7edf84c423a5f25ebb340fcdab552d5784e2109 Mon Sep 17 00:00:00 2001 From: Florian Merz Date: Thu, 11 Feb 2021 14:51:32 +0100 Subject: unslug tr: modify --- files/tr/web/security/mixed_content/index.html | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) (limited to 'files/tr/web/security/mixed_content/index.html') diff --git a/files/tr/web/security/mixed_content/index.html b/files/tr/web/security/mixed_content/index.html index 2576d1c4bf..7b8c6d0a3b 100644 --- a/files/tr/web/security/mixed_content/index.html +++ b/files/tr/web/security/mixed_content/index.html @@ -1,7 +1,8 @@ --- title: Mixed Content -slug: Security/MixedContent +slug: Web/Security/Mixed_content translation_of: Web/Security/Mixed_content +original_slug: Security/MixedContent ---

When a user visits a page served over HTTPS, their connection with the web server is encrypted with SSL and hence safeguarded from sniffers and man-in-the-middle attacks.

If the HTTPS page includes content retrieved through regular, cleartext HTTP, then the connection is only partially encrypted: the unencrypted content is accessible to sniffers and can be modified by man-in-the-middle attackers, and therefore the connection is not safeguarded anymore. When a webpage exhibits this behavior, it is called a mixed content page.

-- cgit v1.2.3-54-g00ecf