Only use example.com as example domain (#41428)

* Only use *.example and example.com as example domains

* Revert changes

* Use non-apex

Author: Josh-Cena

files/en-us/glossary/preflight_request/index.md

@@ -17,15 +17,15 @@ For example, a client might be asking a server if it would allow a {{HTTPMethod(
 OPTIONS /resource/foo
 Access-Control-Request-Method: DELETE
 Access-Control-Request-Headers: x-requested-with
-Origin: https://foo.bar.org
+Origin: https://www.example.com
 ```
 
 If the server allows it, then it will respond to the preflight request with an {{HTTPHeader("Access-Control-Allow-Methods")}} response header, which lists `DELETE`:
 
 ```http
 HTTP/1.1 204 No Content
 Connection: keep-alive
-Access-Control-Allow-Origin: https://foo.bar.org
+Access-Control-Allow-Origin: https://www.example.com
 Access-Control-Allow-Methods: POST, GET, OPTIONS, DELETE
 Access-Control-Allow-Headers: X-Requested-With
 Access-Control-Max-Age: 86400

files/en-us/learn_web_development/extensions/forms/basic_native_form_controls/index.md

@@ -285,7 +285,7 @@ If the image button is used to submit the form, this control doesn't submit its
 So for example when you click on the image at coordinate (123, 456) and it submits via the `get` method, you'll see the values appended to the URL as follows:
 
 ```url
-http://foo.com?pos.x=123&pos.y=456
+https://example.com?pos.x=123&pos.y=456
 ```
 
 This is a very convenient way to build a "hot map". How these values are sent and retrieved is detailed in the [Sending form data](/en-US/docs/Learn_web_development/Extensions/Forms/Sending_and_retrieving_form_data) article.

files/en-us/learn_web_development/extensions/forms/sending_and_retrieving_form_data/index.md

@@ -55,10 +55,10 @@ The {{HTMLElement("form")}} element defines how the data will be sent. All of it
 
 The [`action`](/en-US/docs/Web/HTML/Reference/Elements/form#action) attribute defines where the data gets sent. Its value must be a valid relative or absolute [URL](/en-US/docs/Learn_web_development/Howto/Web_mechanics/What_is_a_URL). If this attribute isn't provided, the data will be sent to the URL of the page containing the form — the current page.
 
-In this example, the data is sent to an absolute URL — `https://example.com`:
+In this example, the data is sent to an absolute URL — `https://www.example.com`:
 
 ```html
-<form action="https://example.com">…</form>
+<form action="https://www.example.com">…</form>
 ```
 
 Here, we use a relative URL — the data is sent to a different URL on the same origin:
@@ -93,7 +93,7 @@ The [`GET` method](/en-US/docs/Web/HTTP/Reference/Methods/GET) is the method use
 Consider the following form:
 
 ```html
-<form action="http://www.foo.com" method="GET">
+<form action="https://www.example.com/greet" method="GET">
   <div>
     <label for="say">What greeting do you want to say?</label>
     <input name="say" id="say" value="Hi" />
@@ -108,7 +108,7 @@ Consider the following form:
 </form>
 ```
 
-Since the `GET` method has been used, you'll see the URL `www.foo.com/?say=Hi&to=Mom` appear in the browser address bar when you submit the form.
+Since the `GET` method has been used, you'll see the URL `https://www.example.com/greet?say=Hi&to=Mom` appear in the browser address bar when you submit the form.
 
 ![The changed url with query parameters after submitting the form with GET method with a "server not found" browser error page](url-parameters.png)
 
@@ -121,7 +121,7 @@ The HTTP request looks like this:
 
 ```http
 GET /?say=Hi&to=Mom HTTP/2.0
-Host: foo.com
+Host: example.com
 ```
 
 > [!NOTE]
@@ -137,7 +137,7 @@ The [`POST` method](/en-US/docs/Web/HTTP/Reference/Methods/POST) is a little dif
 Let's look at an example — this is the same form we looked at in the `GET` section above, but with the [`method`](/en-US/docs/Web/HTML/Reference/Elements/form#method) attribute set to `POST`.
 
 ```html
-<form action="http://www.foo.com" method="POST">
+<form action="https://www.example.com/greet" method="POST">
   <div>
     <label for="say">What greeting do you want to say?</label>
     <input name="say" id="say" value="Hi" />
@@ -156,7 +156,7 @@ When the form is submitted using the `POST` method, you get no data appended to
 
 ```http
 POST / HTTP/2.0
-Host: foo.com
+Host: example.com
 Content-Type: application/x-www-form-urlencoded
 Content-Length: 13
 
@@ -178,7 +178,7 @@ HTTP requests are never displayed to the user (if you want to see them, you need
 1. Open the developer tools.
 2. Select "Network"
 3. Select "All"
-4. Select "foo.com" in the "Name" tab
+4. Select "example.com" in the "Name" tab
 5. Select "Request" (Firefox) or "Payload" (Chrome/Edge)
 
 You can then get the form data, as shown in the image below.
@@ -292,7 +292,10 @@ If you want to send files, you need to take three extra steps:
 For example:
 
 ```html
-<form method="post" action="https://www.foo.com" enctype="multipart/form-data">
+<form
+  method="post"
+  action="https://example.com/upload"
+  enctype="multipart/form-data">
   <div>
     <label for="file">Choose a file</label>
     <input type="file" id="file" name="myFile" />

files/en-us/mozilla/add-ons/webextensions/api/declarativenetrequest/index.md

@@ -37,7 +37,7 @@ The declarative rules are defined by four fields:
 > - the action does not change the request.
 > - the redirect URL is invalid (e.g., the value of {{WebExtAPIRef("declarativeNetRequest.redirect","redirect.regexSubstitution")}} is not a valid URL).
 
-This is an example rule that blocks all script requests originating from `"foo.com"` to any URL with `"abc"` as a substring:
+This is an example rule that blocks all script requests originating from `"example.com"` to any URL with `"abc"` as a substring:
 
 ```json
 {
@@ -46,7 +46,7 @@ This is an example rule that blocks all script requests originating from `"foo.c
   "action": { "type": "block" },
   "condition": {
     "urlFilter": "abc",
-    "initiatorDomains": ["foo.com"],
+    "initiatorDomains": ["example.com"],
     "resourceTypes": ["script"]
   }
 }

files/en-us/web/api/backgroundfetchregistration/match/index.md

@@ -31,7 +31,7 @@ match(request, options)
       - : A boolean value that specifies whether to
         ignore the query string in the URL. For example, if set to
         `true` the `?value=bar` part of
-        `http://foo.com/?value=bar` would be ignored when performing a match.
+        `https://example.com/?value=bar` would be ignored when performing a match.
         It defaults to `false`.
     - `ignoreMethod` {{optional_inline}}
       - : A boolean value. When `true`,

files/en-us/web/api/backgroundfetchregistration/matchall/index.md

@@ -32,7 +32,7 @@ matchAll(request,options)
       - : A boolean value that specifies whether to
         ignore the query string in the URL. For example, if set to
         `true` the `?value=bar` part of
-        `http://foo.com/?value=bar` would be ignored when performing a match.
+        `https://example.com/?value=bar` would be ignored when performing a match.
         It defaults to `false`.
     - `ignoreMethod` {{optional_inline}}
       - : A boolean value. When `true`,

files/en-us/web/api/cache/delete/index.md

@@ -28,7 +28,7 @@ delete(request, options)
     The available options are:
     - `ignoreSearch`
       - : A boolean value that specifies whether the matching process should ignore the query string in the URL.
-        If set to `true`, the `?value=bar` part of `http://foo.com/?value=bar` would be ignored when performing a match.
+        If set to `true`, the `?value=bar` part of `https://example.com/?value=bar` would be ignored when performing a match.
         It defaults to `false`.
     - `ignoreMethod`
       - : A boolean value that, when set to

files/en-us/web/api/cache/keys/index.md

@@ -38,7 +38,7 @@ keys(request, options)
       - : A boolean value that specifies whether the
         matching process should ignore the query string in the URL. If set to
         `true`, the `?value=bar` part of
-        `http://foo.com/?value=bar` would be ignored when performing a match.
+        `https://example.com/?value=bar` would be ignored when performing a match.
         It defaults to `false`.
     - `ignoreMethod`
       - : A boolean value that, when set to

files/en-us/web/api/cache/match/index.md

@@ -30,7 +30,7 @@ match(request, options)
       - : A boolean value that specifies whether to
         ignore the query string in the URL. For example, if set to
         `true` the `?value=bar` part of
-        `http://foo.com/?value=bar` would be ignored when performing a match.
+        `https://example.com/?value=bar` would be ignored when performing a match.
         It defaults to `false`.
     - `ignoreMethod`
       - : A boolean value that, when set to

files/en-us/web/api/cache/matchall/index.md

@@ -33,7 +33,7 @@ matchAll(request, options)
       - : A boolean value that specifies whether the
         matching process should ignore the query string in the URL. If set to
         `true`, the `?value=bar` part of
-        `http://foo.com/?value=bar` would be ignored when performing a match.
+        `https://example.com/?value=bar` would be ignored when performing a match.
         It defaults to `false`.
     - `ignoreMethod`
       - : A boolean value that, when set to