Fix missing images on English pages
Hugo only auto-shares page-bundle resources across translations when each language has its own content directory; with filename-based translation (index.fr.md / index.en.md in the same folder) a resource with no language code is assigned to the default language only. Add .en.-suffixed copies of every image referenced from English pages and point the English markdown at them.
This commit is contained in:
BIN
content/documentation/securité/cadenas_vert/certificat.en.png
Normal file
BIN
content/documentation/securité/cadenas_vert/certificat.en.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 55 KiB |
@@ -10,7 +10,7 @@ cascade:
|
||||
|
||||
You've seen it thousands of times, haven't you? That little **green padlock** (or sometimes gray, depending on your browser and the site) that shows up next to a website's address in your navigation bar. You click on it, you look at it, you think "cool, it's secure," and you move on.
|
||||
|
||||

|
||||

|
||||
|
||||
But... do you really know what it means? 🤔 All the **mechanics that kick in** just so this little symbol appears? It's much more than a simple icon! It's the visible part of an iceberg. \
|
||||
**So, what's our mission today? 🚀**
|
||||
|
||||
File diff suppressed because one or more lines are too long
|
After Width: | Height: | Size: 222 KiB |
File diff suppressed because one or more lines are too long
|
After Width: | Height: | Size: 336 KiB |
File diff suppressed because one or more lines are too long
|
After Width: | Height: | Size: 304 KiB |
@@ -22,7 +22,7 @@ The principle of HTTPS is comparable to sending mail in a safe where only the se
|
||||
|
||||
**SSL Bumping** gets around this problem by inserting itself in the middle of the communication:
|
||||
|
||||

|
||||

|
||||
|
||||
The proxy will:
|
||||
1. **Intercept** the client's HTTPS connection.
|
||||
@@ -57,7 +57,7 @@ For SSL Bumping to work, the proxy must be able to generate certificates on the
|
||||
|
||||
When you try to access `https://www.example.com`:
|
||||
|
||||

|
||||

|
||||
|
||||
1. The proxy intercepts your request.
|
||||
2. It connects to the real `example.com` server and retrieves its legitimate certificate.
|
||||
@@ -77,7 +77,7 @@ To really understand the mechanism, nothing beats hands-on practice. I've prepar
|
||||
|
||||
### Lab Architecture
|
||||
|
||||

|
||||

|
||||
|
||||
### Quick Deployment
|
||||
|
||||
|
||||
Reference in New Issue
Block a user