From 6eeb93afaa54a4d10aa06b683584d99683e5fae1 Mon Sep 17 00:00:00 2001 From: Peter Bengtsson Date: Wed, 7 Jul 2021 12:38:45 -0400 Subject: remove wiki.developer.mozilla.org links (de) (#1441) Part of #1440 --- files/de/web/http/headers/set-cookie/index.html | 4 ++-- files/de/web/http/status/index.html | 2 +- 2 files changed, 3 insertions(+), 3 deletions(-) (limited to 'files/de/web/http') diff --git a/files/de/web/http/headers/set-cookie/index.html b/files/de/web/http/headers/set-cookie/index.html index 529d57a83c..d82bd2a816 100644 --- a/files/de/web/http/headers/set-cookie/index.html +++ b/files/de/web/http/headers/set-cookie/index.html @@ -95,7 +95,7 @@ Set-Cookie: <cookie-name>=<cookie-value>; Domain=<domain-value>
A path that must exist in the requested URL, or the browser won't send the Cookie header.
The forward slash (/) character is interpreted as a directory separator, and subdirectories will be matched as well: for Path=/docs, /docs, /docs/Web/, and /docs/Web/HTTP will all match.
Secure {{optional_inline}}
-
Cookie is only sent to the server when a request is made with the https: scheme (except on localhost), and therefore is more resistent to man-in-the-middle attacks. +
Cookie is only sent to the server when a request is made with the https: scheme (except on localhost), and therefore is more resistent to man-in-the-middle attacks.

Note: Do not assume that Secure prevents all access to sensitive information in cookies (session keys, login details, etc.). Cookies with this attribute can still be read/modified with access to the client's hard disk, or from JavaScript if the HttpOnly cookie attribute is not set.

Note: Insecure sites (http:) can't set cookies with the Secure attribute (since Chrome 52 and Firefox 52). For Firefox, the https: requirements are ignored when the Secure attribute is set by localhost (since Firefox 75).

@@ -114,7 +114,7 @@ Set-Cookie: <cookie-name>=<cookie-value>; Domain=<domain-value> also specify the Secure attribute (i.e. they require a secure context). -

The options below covers the new behaviour. See the Browser compatibility table for information about specific browser implementation (rows: "SameSite: Defaults to Lax" and "SameSite: Secure context required").

+

The options below covers the new behaviour. See the Browser compatibility table for information about specific browser implementation (rows: "SameSite: Defaults to Lax" and "SameSite: Secure context required").

Inline options are: diff --git a/files/de/web/http/status/index.html b/files/de/web/http/status/index.html index 91ae3cda58..677b3d112b 100644 --- a/files/de/web/http/status/index.html +++ b/files/de/web/http/status/index.html @@ -32,7 +32,7 @@ translation_of: Web/HTTP/Status
{{HTTPStatus(102, "102 Processing")}} ({{Glossary("WebDAV")}})
Dieser Code zeigt an, dass der Server die Anfrage erhalten hat und bearbeitet, aber noch keine Antwort verfügbar ist.
{{HTTPStatus(103, "103 Early Hints")}}
-
Dieser Statuscode ist in erster Linie für die Verwendung mit dem {{HTTPHeader("Link")}} Header vorgesehen, damit der Benutzeragent mit dem Vorladen von Ressourcen beginnen kann, während der Server eine Antwort vorbereitet.
+
Dieser Statuscode ist in erster Linie für die Verwendung mit dem {{HTTPHeader("Link")}} Header vorgesehen, damit der Benutzeragent mit dem Vorladen von Ressourcen beginnen kann, während der Server eine Antwort vorbereitet.

Erfolgreiche Antworten

-- cgit v1.2.3-54-g00ecf