You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: pages/apple-silicon/how-to/remove-public-ip.mdx
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,7 +8,7 @@ content:
8
8
tags: mac-mini private network bastion
9
9
dates:
10
10
validation: 2025-05-13
11
-
posted: 2022-05-13
11
+
posted: 2025-05-13
12
12
categories:
13
13
- bare-metal
14
14
---
@@ -69,4 +69,4 @@ Once you have verified that your Mac mini is reachable through the Bastion, you
69
69
Your Mac mini is now fully isolated from the public internet, and any further external access will have to occur from a resource inside the Private Network or through the Bastion.
70
70
<Messagetype="tip">
71
71
Your Mac mini will still be able to access the internet through the gateway if needed.
Copy file name to clipboardExpand all lines: pages/load-balancer/reference-content/acls.mdx
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,13 +1,13 @@
1
1
---
2
2
meta:
3
3
title: Understanding Access Control Lists (ACLs)
4
-
description: Learn more about Access Control Lists (ACLs) for your Load Balancer
4
+
description: Discover how Access Control Lists (ACLs) work with your Load Balancer at Scaleway, and learn how to configure them for secure and efficient traffic management.
5
5
content:
6
6
h1: Understanding Access Control Lists (ACLs)
7
-
paragraph: Learn more about Access Control Lists (ACLs) for your Load Balancer
7
+
paragraph: Discover how Access Control Lists (ACLs) work with your Load Balancer at Scaleway, and learn how to configure them for secure and efficient traffic management.
Copy file name to clipboardExpand all lines: pages/load-balancer/reference-content/http2-http3.mdx
+7-7Lines changed: 7 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,13 +1,13 @@
1
1
---
2
2
meta:
3
3
title: Setting up your Load Balancer for HTTP/2 or HTTP/3
4
-
description: Learn how to set up your Load Balancer for HTTP/2 or HTTP/3
4
+
description: Learn how to configure HTTP/2 and HTTP/3 protocols on your Scaleway Load Balancer to improve performance, security, and user experience for your web applications.
5
5
content:
6
6
h1: Setting up your Load Balancer for HTTP/2 or HTTP/3
7
-
paragraph: Learn how to set up your Load Balancer for HTTP/2 or HTTP/3
7
+
paragraph: Learn how to configure HTTP/2 and HTTP/3 protocols on your Scaleway Load Balancer to improve performance, security, and user experience for your web applications.
@@ -23,7 +23,7 @@ Development of the first version of the HTTP protocol, HTTP/1, began in 1989. Th
23
23
24
24
### HTTP/2
25
25
26
-
HTTP/2 was released in 2015. It represents a more efficient version of HTTP, moving from a text based protocol to a binary protocol. This is easier to parse for clients and servers, helps avoid errors and allows for multiplexing. Over [40% of websites now use HTTP/2/](https://w3techs.com/technologies/details/ce-http2), and it is supported by [97% of web browsers](https://caniuse.com/?search=http2).
26
+
HTTP/2 was released in 2015. It represents a more efficient version of HTTP, moving from a text based protocol to a binary protocol. This is easier to parse for clients and servers, helps avoid errors and allows for multiplexing. Over [40% of websites now use HTTP/2](https://w3techs.com/technologies/details/ce-http2), and it is supported by [97% of web browsers](https://caniuse.com/?search=http2).
27
27
28
28
HTTP/2 improves upon HTTP/1's performance in many ways, including but not limited to:
29
29
-**Increased efficiency via use of binary framing**. HTTP/1 uses text-based data transfer, which can be long, bandwidth-heavy and error-prone. HTTP/2 uses binary message framing, which is more compact and efficient so easier to parse, and provokes fewer errors.
@@ -40,9 +40,9 @@ Backends and frontends of Scaleway Load Balancers support HTTP/1, HTTP/2 and HTT
40
40
41
41
|| Frontend with TLS | Frontend without TLS | Backend with TLS | Backend without TLS |
0 commit comments