docs: update http links to https (fastify#3976)

Author: Fdawgs

README.md

@@ -292,7 +292,7 @@ This project is kindly sponsored by:
 - [nearForm](https://nearform.com)
 
 Past Sponsors:
-- [LetzDoIt](http://www.letzdoitapp.com/)
+- [LetzDoIt](https://www.letzdoitapp.com/)
 
 ## License
 

docs/Guides/Prototype-Poisoning.md

@@ -359,7 +359,7 @@ address.
 We also got lucky by having full access to mitigate it at the source — didn't
 need to send emails to some unknown framework maintainer and hope for a quick
 answer. hapi's total control over all of its dependencies proved its usefulness
-and security again. Not using [hapi](http://hapijs.com)? [Maybe you
+and security again. Not using [hapi](https://hapi.dev)? [Maybe you
 should](https://hueniverse.com/why-you-should-consider-hapi-6163689bd7c2).
 
 ### The after in happy ever-after

docs/Guides/Recommendations.md

@@ -172,7 +172,7 @@ backend static-backend
 # with 2 primary servers distributed via round-robin
 # and one backup which is used when the first 2 are not reachable
 # This also assumes your fastify servers are listening on port 80.
-# more info: http://nginx.org/en/docs/http/ngx_http_upstream_module.html
+# more info: https://nginx.org/en/docs/http/ngx_http_upstream_module.html
 upstream fastify_app {
   server 10.10.11.1:80;
   server 10.10.11.2:80;
@@ -257,7 +257,7 @@ server {
   # trustProxy to the address of your NGINX server so the X-Forwarded
   # fields are used by fastify.
   location / {
-    # more info: http://nginx.org/en/docs/http/ngx_http_proxy_module.html
+    # more info: https://nginx.org/en/docs/http/ngx_http_proxy_module.html
     proxy_http_version 1.1;
     proxy_cache_bypass $http_upgrade;
     proxy_set_header Upgrade $http_upgrade;

docs/Reference/Routes.md

@@ -540,7 +540,7 @@ You can provide a `version` key in the `constraints` option to a route.
 Versioned routes allow you to declare multiple handlers for the same HTTP route
 path, which will then be matched according to each request's `Accept-Version`
 header. The `Accept-Version` header value should follow the
-[semver](http://semver.org/) specification, and routes should be declared with
+[semver](https://semver.org/) specification, and routes should be declared with
 exact semver versions for matching.
 
 Fastify will require a request `Accept-Version` header to be set if the route