Update RFC links

adriendupuis · adriendupuis · commit 3806f5e06c9e · 2025-03-03T15:50:17.000+01:00
diff --git a/docs/api/rest_api_authentication.md b/docs/api/rest_api_authentication.md
@@ -353,7 +353,7 @@ you can get the JWT token through the following request:
 
 ## HTTP basic authentication
 
-For more information, see [HTTP Authentication: Basic and Digest Access Authentication](http://tools.ietf.org/html/rfc2617).
+For more information, see [HTTP Authentication: Basic and Digest Access Authentication](https://datatracker.ietf.org/doc/html/rfc2617).
 
 ### Configuration
 
@@ -381,7 +381,7 @@ If the installation has a dedicated host for REST, you can enable HTTP basic aut
 ### Usage example
 
 Basic authentication requires the username and password to be sent *(username:password)*, base64 encoded, with each request.
-For details, see [RFC 2617](http://tools.ietf.org/html/rfc2617).
+For details, see [RFC 2617](https://datatracker.ietf.org/doc/html/rfc2617).
 
 Most HTTP client libraries as well as REST libraries support this method.
 [Creating content with binary attachments](rest_api_requests.md#creating-content-with-binary-attachments) has an example using basic authentication with [cURL](https://www.php.net/manual/en/book.curl.php) and its `CURLOPT_USERPWD`. 
diff --git a/docs/api/rest_api_requests.md b/docs/api/rest_api_requests.md
@@ -20,18 +20,18 @@ Depending on the HTTP method used, different actions will be possible on the sam
 The following list of available methods gives an overview of the kind of action a method triggers on a resource, if available.
 For method action details per resource, see the [REST API reference](rest_api_reference/rest_api_reference.html).
 
-| HTTP method                                                | Status   | Description            | Safe |
-|------------------------------------------------------------|----------|------------------------|------|
-| [OPTIONS](https://tools.ietf.org/html/rfc2616#section-9.2) | Standard | List available methods | Yes  |
-| [GET](https://tools.ietf.org/html/rfc2616#section-9.3)     | Standard | Collect data           | Yes  |
-| [HEAD](https://tools.ietf.org/html/rfc2616#section-9.4)    | Standard | Check existence        | Yes  |
-| [POST](https://tools.ietf.org/html/rfc2616#section-9.5)    | Standard | Create an item         | No   |
-| [PATCH](http://tools.ietf.org/html/rfc5789)                | Custom   | Update an item         | No   |
-| COPY                                                       | Custom   | Duplicate an item      | No   |
-| [MOVE](http://tools.ietf.org/html/rfc2518)                 | Custom   | Move an item           | No   |
-| SWAP                                                       | Custom   | Swap two Locations     | No   |
-| PUBLISH                                                    | Custom   | Publish an item        | No   |
-| [DELETE](https://tools.ietf.org/html/rfc2616#section-9.7)  | Standard | Remove an item         | No   |
+| HTTP method                                                         | Status   | Description            | Safe |
+|---------------------------------------------------------------------|----------|------------------------|------|
+| [OPTIONS](https://datatracker.ietf.org/doc/html/rfc2616#section-9.2) | Standard | List available methods | Yes  |
+| [GET](https://datatracker.ietf.org/doc/html/rfc2616#section-9.3)    | Standard | Collect data           | Yes  |
+| [HEAD](https://datatracker.ietf.org/doc/html/rfc2616#section-9.4)   | Standard | Check existence        | Yes  |
+| [POST](https://datatracker.ietf.org/doc/html/rfc2616#section-9.5)   | Standard | Create an item         | No   |
+| [PATCH](https://datatracker.ietf.org/doc/html/rfc5789)              | Custom   | Update an item         | No   |
+| COPY                                                                | Custom   | Duplicate an item      | No   |
+| [MOVE](https://datatracker.ietf.org/doc/html/rfc2518)               | Custom   | Move an item           | No   |
+| SWAP                                                                | Custom   | Swap two Locations     | No   |
+| PUBLISH                                                             | Custom   | Publish an item        | No   |
+| [DELETE](https://datatracker.ietf.org/doc/html/rfc2616#section-9.7) | Standard | Remove an item         | No   |
 
 !!! note "Caution with custom HTTP methods"
 
@@ -47,7 +47,7 @@ Unsafe methods will require a CSRF token if [session-based authentication](rest_
 
 Any URI resource that the REST API responds to will respond to an `OPTIONS` request.
 
-The response contains an [`Allow` header](https://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.7), which lists the methods accepted by the resource.
+The response contains an [`Allow` header](https://www.rfc-editor.org/rfc/rfc9110.html#name-allow), which lists the methods accepted by the resource.
 
 ```shell
 curl -IX OPTIONS https://api.example.com/api/ezp/v2/content/objects/1
@@ -81,8 +81,8 @@ Allow: GET,PATCH,DELETE,COPY,MOVE,SWAP
 
 You can use the following HTTP headers with a REST request:
 
-- [`Accept`](https://tools.ietf.org/html/rfc2616#section-14.1) describing the desired response type and format;
-- [`Content-Type`](https://toos.ietf.org/html/rfc2616#section-14.17) describing the payload type and format;
+- [`Accept`](https://datatracker.ietf.org/doc/html/rfc2616#section-14.1) describing the desired response type and format;
+- [`Content-Type`](https://datatracker.ietf.org/doc/html/rfc2616#section-14.17) describing the payload type and format;
 - [`X-Siteaccess`](#siteaccess) specifying the target SiteAccess;
 - `X-HTTP-Method-Override` allowing to pass a custom method while using `POST` method as previously seen in [HTTP method](#request-method).
 - [`Destination`](#destination) specifying where to move an item
@@ -114,8 +114,8 @@ On top of methods, HTTP request headers allow you to personalize the request's b
 On every resource, you can use the `Accept` header to indicate which format you want to communicate in, JSON or XML.
 This header is also used to specify the response type you want the server to send when multiple types are available.
 
--   `Accept: application/vnd.ez.api.Content+xml` to get `Content` (full data, Fields included) as **[XML](http://www.w3.org/XML/)**
--   `Accept: application/vnd.ez.api.ContentInfo+json` to get `ContentInfo` (metadata only) as **[JSON](http://www.json.org/)**
+-   `Accept: application/vnd.ez.api.Content+xml` to get `Content` (full data, Fields included) as **[XML](https://www.w3.org/XML/)**
+-   `Accept: application/vnd.ez.api.ContentInfo+json` to get `ContentInfo` (metadata only) as **[JSON](https://www.json.org/)**
 
 Media types are also used with the [`Content-Type` header](rest_api_responses.md#content-type-header) to characterize a [request body](#request-body) or a [response body](rest_api_responses.md#response-body).
 See [Creating content with binary attachments](#creating-content-with-binary-attachments) below.
@@ -142,11 +142,11 @@ You can pass some short scalar parameters in the URIs or as GET parameters, but
 in particular the ones to create (`POST`) or update (`PATCH`) items.
 In the [REST API reference](rest_api_reference/rest_api_reference.html), request payload examples are given when needed.
 
-One example is the [creation of an authentication session](rest_api_authentication.md#establishing-a-session).
+One example is the [creation of an authentication session](rest_api_authentication.md#establishing-session).
 
 When creating a Content item, a special payload is needed if the ContentType has some [Image](field_types_reference/imagefield.md) or [BinaryFile](field_types_reference/binaryfilefield.md) Fields as files need to be attached. See the example of a [script uploading images](#creating-content-with-binary-attachments) below.
 
-When searching for Content items (or Locations), the query grammar is also particular. See the [Search section](#search-view) below.
+When searching for Content items (or Locations), the query grammar is also particular. See the [Search section](#search-views) below.
 
 ### Creating content with binary attachments
 
diff --git a/docs/guide/personalization/developer_guide/recommendation_api.md b/docs/guide/personalization/developer_guide/recommendation_api.md
@@ -40,7 +40,7 @@ For the request to return recommendations, you must provide the following parame
 ### Customizing the recommendation request
 
 You can customize the recommendation request by using additional query string parameters. 
-For example, you can send the following request to the recommendation engine: 
+For example, you can send the following request to the recommendation engine:
 
 `GET https://reco.yoochoose.net/api/v2/00000/john.doe/landing_page.json ?contextitems=123&categorypath=%2FCamera%2FCompact&attribute=title&attribute=deeplink,description&numrecs=8`
 
@@ -258,7 +258,7 @@ Error messages can change, do not use them for automated processing.
 
 In most cases the recommendation engine's response can be cached. 
 Depending on the recommendation model and context, it can drastically reduce the number of recommendation requests. 
-The recommendation service supports the following HTTP headers to enable cache control on the client side (all date values must follow the "HTTP-date" format as defined by [RFC 2616](https://tools.ietf.org/html/rfc2616)):
+The recommendation service supports the following HTTP headers to enable cache control on the client side (all date values must follow the "HTTP-date" format as defined by [RFC 2616](https://datatracker.ietf.org/doc/html/rfc2616)):
 
 |Scope|Header|Description|Example|
 |---|---|---|---|
