docs: update links (fastify#6593)

* docs: update links

* docs: update links

* docs: update links

* docs: update links

* docs: update links

* docs: update links

Author: Tony133

docs/Guides/Migration-Guide-V5.md

@@ -540,7 +540,7 @@ and [#4682](https://github.com/fastify/fastify/issues/4682) for more information
 The `getDefaultRoute` and `setDefaultRoute` methods have been removed in v5.
 
 See [#4485](https://github.com/fastify/fastify/pull/4485)
-and [#4480](https://github.com/fastify/fastify/pull/4485)
+and [#4480](https://github.com/fastify/fastify/pull/4480)
 for more information.
 This was already deprecated in v4 as `FSTDEP014`,
 so you should have already updated your code.

docs/Reference/Errors.md

@@ -109,12 +109,12 @@
 #### Uncaught Errors
 In Node.js, uncaught errors can cause memory leaks, file descriptor leaks, and
 other major production issues.
-[Domains](https://nodejs.org/en/docs/guides/domain-postmortem/) were a failed
+[Domains](https://nodejs.org/en/blog/community/domain-postmortem) were a failed
 attempt to fix this.
 
 Given that it is not possible to process all uncaught errors sensibly, the best
 way to deal with them is to
-[crash](https://nodejs.org/api/process.html#process_warning_using_uncaughtexception_correctly).
+[crash](https://nodejs.org/api/process.html#warning-using-uncaughtexception-correctly).
 
 #### Catching Errors In Promises
 When using promises, attach a `.catch()` handler synchronously.
@@ -312,7 +312,7 @@ Below is a table with all the error codes used by Fastify.
 | <a id="fst_err_dec_missing_dependency">FST_ERR_DEC_MISSING_DEPENDENCY</a> | The decorator cannot be registered due to a missing dependency. | Register the missing dependency. | [#1168](https://github.com/fastify/fastify/pull/1168) |
 | <a id="fst_err_dec_after_start">FST_ERR_DEC_AFTER_START</a> | The decorator cannot be added after start. | Add the decorator before starting the server. | [#2128](https://github.com/fastify/fastify/pull/2128) |
 | <a id="fst_err_dec_reference_type">FST_ERR_DEC_REFERENCE_TYPE</a> | The decorator cannot be a reference type. | Define the decorator with a getter/setter interface or an empty decorator with a hook. | [#5462](https://github.com/fastify/fastify/pull/5462) |
-| <a id="fst_err_dec_undeclared">FST_ERR_DEC_UNDECLARED</a> | An attempt was made to access a decorator that has not been declared. | Declare the decorator before using it. | [#](https://github.com/fastify/fastify/pull/)
+| <a id="fst_err_dec_undeclared">FST_ERR_DEC_UNDECLARED</a> | An attempt was made to access a decorator that has not been declared. | Declare the decorator before using it. | [#5768](https://github.com/fastify/fastify/pull/5768)
 | <a id="fst_err_hook_invalid_type">FST_ERR_HOOK_INVALID_TYPE</a> | The hook name must be a string. | Use a string for the hook name. | [#1168](https://github.com/fastify/fastify/pull/1168) |
 | <a id="fst_err_hook_invalid_handler">FST_ERR_HOOK_INVALID_HANDLER</a> | The hook callback must be a function. | Use a function for the hook callback. | [#1168](https://github.com/fastify/fastify/pull/1168) |
 | <a id="fst_err_hook_invalid_async_handler">FST_ERR_HOOK_INVALID_ASYNC_HANDLER</a> | Async function has too many arguments. Async hooks should not use the `done` argument. | Remove the `done` argument from the async hook. | [#4367](https://github.com/fastify/fastify/pull/4367) |

docs/Reference/Server.md

@@ -143,7 +143,7 @@ This option also applies when the [`http2`](#factory-http2) option is set.
 
 Defines the server timeout in milliseconds. See documentation for
 [`server.timeout`
-property](https://nodejs.org/api/http.html#http_server_timeout) to understand
+property](https://nodejs.org/api/http.html#servertimeout) to understand
 the effect of this option.
 
 When `serverFactory` option is specified this option is ignored.
@@ -155,7 +155,7 @@ When `serverFactory` option is specified this option is ignored.
 
 Defines the server keep-alive timeout in milliseconds. See documentation for
 [`server.keepAliveTimeout`
-property](https://nodejs.org/api/http.html#http_server_keepalivetimeout) to
+property](https://nodejs.org/api/http.html#serverkeepalivetimeout) to
 understand the effect of this option. This option only applies when HTTP/1 is in
 use.
 
@@ -198,7 +198,7 @@ method, otherwise attempting to set it will throw an exception.
 
 Defines the maximum number of requests a socket can handle before closing keep
 alive connection. See [`server.maxRequestsPerSocket`
-property](https://nodejs.org/dist/latest/docs/api/http.html#http_server_maxrequestspersocket)
+property](https://nodejs.org/dist/latest/docs/api/http.html#servermaxrequestspersocket)
 to understand the effect of this option. This option only applies when HTTP/1.1
 is in use. Also, when `serverFactory` option is specified, this option is
 ignored.
@@ -213,7 +213,7 @@ ignored.
 
 Defines the maximum number of milliseconds for receiving the entire request from
 the client. See [`server.requestTimeout`
-property](https://nodejs.org/dist/latest/docs/api/http.html#http_server_requesttimeout)
+property](https://nodejs.org/dist/latest/docs/api/http.html#servertimeout)
 to understand the effect of this option.
 
 When `serverFactory` option is specified, this option is ignored.
@@ -335,7 +335,7 @@ This property is used to configure the internal logger instance.
 The possible values this property may have are:
 
 + Default: `false`. The logger is disabled. All logging methods will point to a
-  null logger [abstract-logging](https://npm.im/abstract-logging) instance.
+null logger [abstract-logging](https://www.npmjs.com/package/abstract-logging) instance.
 
 + `object`: a standard Pino [options
   object](https://github.com/pinojs/pino/blob/c77d8ec5ce/docs/API.md#constructor).
@@ -730,7 +730,7 @@ const fastify = require('fastify')({
 <a id="client-error-handler"></a>
 
 Set a
-[clientErrorHandler](https://nodejs.org/api/http.html#http_event_clienterror)
+[clientErrorHandler](https://nodejs.org/api/http.html#event-clienterror)
 that listens to `error` events emitted by client connections and responds with a
 `400`.
 
@@ -1013,7 +1013,7 @@ be invoked.
 
 This can be useful especially if you have a regex-based route, protecting you
 against [ReDoS
-attacks](https://www.owasp.org/index.php/Regular_expression_Denial_of_Service_-_ReDoS).
+attacks](https://owasp.org/www-community/attacks/Regular_expression_Denial_of_Service_-_ReDoS).
 
 
 ### `onBadUrl`
@@ -1129,7 +1129,7 @@ app.setErrorHandler(function anotherErrorHandler () {
 <a id="server"></a>
 
 `fastify.server`: The Node core
-[server](https://nodejs.org/api/http.html#http_class_http_server) object as
+[server](https://nodejs.org/api/http.html#class-httpserver) object as
 returned by the [**`Fastify factory function`**](#factory).
 
 > ⚠ Warning:
@@ -1243,7 +1243,7 @@ addresses](https://nodejs.org/api/net.html#serverlistenport-host-backlog-callbac
 
 Be careful when deciding to listen on all interfaces; it comes with inherent
 [security
-risks](https://web.archive.org/web/20170831174611/https://snyk.io/blog/mongodb-hack-and-secure-defaults/).
+risks](https://web.archive.org/web/20170711105010/https://snyk.io/blog/mongodb-hack-and-secure-defaults/).
 
 The default is to listen on `port: 0` (which picks the first available open
 port) and `host: 'localhost'`:
@@ -2283,7 +2283,7 @@ test('Uses app and closes it afterwards', async () => {
 In the above example, Fastify is closed automatically after the test finishes.
 
 Read more about the
-[ECMAScript Explicit Resource Management](https://tc39.es/proposal-explicit-resource-management)
+[ECMAScript Explicit Resource Management](https://tc39.es/proposal-explicit-resource-management/)
 and the [using keyword](https://devblogs.microsoft.com/typescript/announcing-typescript-5-2/)
 introduced in TypeScript 5.2.
 

docs/Reference/Warnings.md

@@ -18,8 +18,8 @@ Fastify uses Node.js's [warning event](https://nodejs.org/api/process.html#event
 API to notify users of deprecated features and coding mistakes. Fastify's
 warnings are recognizable by the `FSTWRN` and `FSTDEP` prefixes. When
 encountering such a warning, it is highly recommended to determine the cause
-using the [`--trace-warnings`](https://nodejs.org/api/cli.html#--trace-warnings)
-and [`--trace-deprecation`](https://nodejs.org/api/cli.html#--trace-deprecation)
+using the [`--trace-warnings`](https://nodejs.org/api/cli.html#trace-warnings)
+and [`--trace-deprecation`](https://nodejs.org/api/cli.html#trace-deprecation)
 flags. These produce stack traces pointing to where the issue occurs in the
 application's code. Issues opened about warnings without this information will
 be closed due to lack of details.
@@ -48,9 +48,9 @@ experienced users should consider disabling warnings.
 
 Deprecation codes are supported by the Node.js CLI options:
 
-- [--no-deprecation](https://nodejs.org/api/cli.html#--no-deprecation)
-- [--throw-deprecation](https://nodejs.org/api/cli.html#--throw-deprecation)
-- [--trace-deprecation](https://nodejs.org/api/cli.html#--trace-deprecation)
+- [--no-deprecation](https://nodejs.org/api/cli.html#no-deprecation)
+- [--throw-deprecation](https://nodejs.org/api/cli.html#throw-deprecation)
+- [--trace-deprecation](https://nodejs.org/api/cli.html#trace-deprecation)
 
 
 | Code | Description | How to solve | Discussion |

fastify.js

@@ -922,7 +922,7 @@ function defaultBuildPrettyMeta (route) {
 
 function defaultClientErrorHandler (err, socket) {
   // In case of a connection reset, the socket has been destroyed and there is nothing that needs to be done.
-  // https://nodejs.org/api/http.html#http_event_clienterror
+  // https://nodejs.org/api/http.html#event-clienterror
   if (err.code === 'ECONNRESET' || socket.destroyed) {
     return
   }