diff --git a/pages/network/content_delivery_network_infrastructure/first_domain_name_configuration/guide.de-de.md b/pages/network/content_delivery_network_infrastructure/first_domain_name_configuration/guide.de-de.md index 2ab1e1c4972..1e0b18b610f 100644 --- a/pages/network/content_delivery_network_infrastructure/first_domain_name_configuration/guide.de-de.md +++ b/pages/network/content_delivery_network_infrastructure/first_domain_name_configuration/guide.de-de.md @@ -12,9 +12,9 @@ Bei der ersten Konfiguration des Content Delivery Network (CDN) müssen zunächs ## Voraussetzungen -- Sie nutzen das [OVH Content Delivery Network (CDN)](/links/network/cdn-infrastructure){.external}. +- Sie nutzen das [OVH Content Delivery Network (CDN)](/links/network/cdn-infrastructure). - Sie haben Zugriff auf die Verwaltung der DNS-Zone Ihrer Domain. -- Sie haben Zugriff auf Ihr [OVHcloud Kundencenter](/links/manager){.external}. +- Sie haben Zugriff auf Ihr [OVHcloud Kundencenter](/links/manager). ## Beschreibung @@ -22,7 +22,7 @@ Bei der ersten Konfiguration des Content Delivery Network (CDN) müssen zunächs Fügen Sie dem CDN zunächst eine Subdomain Ihrer Wahl hinzu, damit es HTTP(S)-Anfragen für diese Domain akzeptiert. -Gehen Sie dazu im [OVHcloud Kundencenter ](/links/manager){.external} in den Bereich `Dedicated`{.action} und dann auf `NAS und CDN`{.action}. +Gehen Sie dazu im [OVHcloud Kundencenter ](/links/manager) in den Bereich `Dedicated`{.action} und dann auf `NAS und CDN`{.action}. Klicken Sie auf `Eine Domain zum CDN hinzufügen`{.action}: diff --git a/pages/network/content_delivery_network_infrastructure/first_domain_name_configuration/guide.en-gb.md b/pages/network/content_delivery_network_infrastructure/first_domain_name_configuration/guide.en-gb.md index ab9ca2642d9..af397b6b432 100644 --- a/pages/network/content_delivery_network_infrastructure/first_domain_name_configuration/guide.en-gb.md +++ b/pages/network/content_delivery_network_infrastructure/first_domain_name_configuration/guide.en-gb.md @@ -12,8 +12,8 @@ When you configure the Content Delivery Network (CDN) for the first time, you ne ## Requirements -- an [OVH Content Delivery Network (CDN)](/links/network/cdn-infrastructure){.external} solution -- access to the [OVH Control Panel](/links/manager){.external} +- an [OVH Content Delivery Network (CDN)](/links/network/cdn-infrastructure) solution +- access to the [OVH Control Panel](/links/manager) - the permissions needed to manage your domain’s DNS zone @@ -24,7 +24,7 @@ When you configure the Content Delivery Network (CDN) for the first time, you ne The first step of this configuration involves adding your subdomain to the CDN, so that it accepts HTTP(S) requests. -To do this, go to the [OVH Control Panel](/links/manager){.external}, click on the `Dedicated`{.action} tab, then go to `NAS and CDN`{.action}. +To do this, go to the [OVH Control Panel](/links/manager), click on the `Dedicated`{.action} tab, then go to `NAS and CDN`{.action}. Next, click `Add a domain to the CDN`{.action}. diff --git a/pages/network/content_delivery_network_infrastructure/first_domain_name_configuration/guide.es-es.md b/pages/network/content_delivery_network_infrastructure/first_domain_name_configuration/guide.es-es.md index 5710a6605ee..8ef042eaa91 100644 --- a/pages/network/content_delivery_network_infrastructure/first_domain_name_configuration/guide.es-es.md +++ b/pages/network/content_delivery_network_infrastructure/first_domain_name_configuration/guide.es-es.md @@ -12,9 +12,9 @@ Para empezar a utilizar la solución Content Delivery Network (CDN) de OVH, es n ## Requisitos -- Tener contratada la solución [CDN de OVH](/links/network/cdn-infrastructure){.external}. +- Tener contratada la solución [CDN de OVH](/links/network/cdn-infrastructure). - Tener acceso a la gestión de la zona DNS del dominio. -- Tener acceso al [área de cliente](/links/manager){.external}. +- Tener acceso al [área de cliente](/links/manager). ## Procedimiento @@ -22,7 +22,7 @@ Para empezar a utilizar la solución Content Delivery Network (CDN) de OVH, es n En primer lugar, es necesario añadir el subdominio a la CDN para que esta última acepte las peticiones HTTP(S) relativas al mismo. -Para ello, en el [área de cliente de OVH](/links/manager){.external} acceda a la sección `Dedicado`{.action}. En la columna izquierda, haga clic en `NAS y CDN`{.action} y seleccione el servicio CDN correspondiente. +Para ello, en el [área de cliente de OVH](/links/manager) acceda a la sección `Dedicado`{.action}. En la columna izquierda, haga clic en `NAS y CDN`{.action} y seleccione el servicio CDN correspondiente. Haga clic en el atajo `Añadir un dominio a la CDN`{.action}. diff --git a/pages/network/content_delivery_network_infrastructure/first_domain_name_configuration/guide.fr-fr.md b/pages/network/content_delivery_network_infrastructure/first_domain_name_configuration/guide.fr-fr.md index a4b391db2ac..45ae041cc47 100644 --- a/pages/network/content_delivery_network_infrastructure/first_domain_name_configuration/guide.fr-fr.md +++ b/pages/network/content_delivery_network_infrastructure/first_domain_name_configuration/guide.fr-fr.md @@ -12,9 +12,9 @@ Lors de la première configuration du Content Delivery Network (CDN), il est né ## Prérequis -- Bénéficier du [Content Delivery Network (CDN) d'OVH](/links/network/cdn-infrastructure){.external}. +- Bénéficier du [Content Delivery Network (CDN) d'OVH](/links/network/cdn-infrastructure). - Avoir accès à la gestion de la zone DNS de votre nom de domaine. -- Avoir accès à votre [espace client OVH](/links/manager){.external}. +- Avoir accès à votre [espace client OVH](/links/manager). ## En pratique @@ -22,7 +22,7 @@ Lors de la première configuration du Content Delivery Network (CDN), il est né La première étape de cette configuration est l'ajout du sous-domaine de votre choix au CDN pour que celui-ci accepte les requêtes HTTP(S) pour ce domaine. -Pour cela, rendez-vous dans votre [espace client OVH](/links/manager){.external} dans l'onglet `Dédié`{.action}, puis `NAS et CDN`{.action}. +Pour cela, rendez-vous dans votre [espace client OVH](/links/manager) dans l'onglet `Dédié`{.action}, puis `NAS et CDN`{.action}. Cliquez ensuite sur `Ajouter un domaine au CDN`{.action} : diff --git a/pages/network/content_delivery_network_infrastructure/first_domain_name_configuration/guide.it-it.md b/pages/network/content_delivery_network_infrastructure/first_domain_name_configuration/guide.it-it.md index 6a573e724c3..bedca44172a 100644 --- a/pages/network/content_delivery_network_infrastructure/first_domain_name_configuration/guide.it-it.md +++ b/pages/network/content_delivery_network_infrastructure/first_domain_name_configuration/guide.it-it.md @@ -12,15 +12,15 @@ Per iniziare a utilizzare il servizio Content Delivery Network (CDN) di OVH, è ## Prerequisiti -- Usufruire della [Content Delivery Network (CDN) OVH](https://www.ovh.it/cdn/){.external} +- Usufruire della [Content Delivery Network (CDN) OVH](https://www.ovh.it/cdn/) - Avere accesso alla gestione della zona DNS del dominio -- Avere accesso allo [Spazio Cliente OVH](/links/manager){.external}. +- Avere accesso allo [Spazio Cliente OVH](/links/manager). ## Procedura ### Aggiungi il dominio sulla CDN -Per prima cosa, è necessario aggiungere un sottodominio alla CDN in modo che possa accettare richieste HTTP(S) per questo dominio: accedi alla sezione `Dedicato`{.action} dello [Spazio Cliente OVH](/links/manager){.external} e clicca su `NAS e CDN`{.action} nel menu a sinistra. +Per prima cosa, è necessario aggiungere un sottodominio alla CDN in modo che possa accettare richieste HTTP(S) per questo dominio: accedi alla sezione `Dedicato`{.action} dello [Spazio Cliente OVH](/links/manager) e clicca su `NAS e CDN`{.action} nel menu a sinistra. Clicca su `Aggiungi un dominio alla CDN`{.action}: diff --git a/pages/network/content_delivery_network_infrastructure/first_domain_name_configuration/guide.pl-pl.md b/pages/network/content_delivery_network_infrastructure/first_domain_name_configuration/guide.pl-pl.md index 857cb1b1ee5..f44e0a92a29 100644 --- a/pages/network/content_delivery_network_infrastructure/first_domain_name_configuration/guide.pl-pl.md +++ b/pages/network/content_delivery_network_infrastructure/first_domain_name_configuration/guide.pl-pl.md @@ -12,9 +12,9 @@ Podczas pierwszej konfiguracji usługi CDN (Content Delivery Network) konieczne ## Wymagania początkowe -- Posiadanie usługi [CDN (Content Delivery Network) od OVH](/links/network/cdn-infrastructure){.external} +- Posiadanie usługi [CDN (Content Delivery Network) od OVH](/links/network/cdn-infrastructure) - Dostęp do interfejsu zarządzania strefą DNS Twojej domeny -- Dostęp do [Panelu klienta OVH](/links/manager){.external} +- Dostęp do [Panelu klienta OVH](/links/manager) ## W praktyce @@ -22,7 +22,7 @@ Podczas pierwszej konfiguracji usługi CDN (Content Delivery Network) konieczne Pierwszy etap konfiguracji polega na dodaniu wybranej przez Ciebie subdomeny do usługi CDN, aby mogła ona przyjmować zapytania HTTP(S) dla tej domeny. -W tym celu przejdź do [Panelu klienta](/links/manager){.external} > zakładka `Serwery dedykowane`{.action} > `NAS i CDN`{.action}. +W tym celu przejdź do [Panelu klienta](/links/manager) > zakładka `Serwery dedykowane`{.action} > `NAS i CDN`{.action}. Następnie kliknij `Dodanie domeny do CDN`{.action}: diff --git a/pages/network/content_delivery_network_infrastructure/first_domain_name_configuration/guide.pt-pt.md b/pages/network/content_delivery_network_infrastructure/first_domain_name_configuration/guide.pt-pt.md index 20ceba9f0d1..bca268801a9 100644 --- a/pages/network/content_delivery_network_infrastructure/first_domain_name_configuration/guide.pt-pt.md +++ b/pages/network/content_delivery_network_infrastructure/first_domain_name_configuration/guide.pt-pt.md @@ -12,9 +12,9 @@ Ao configurar a solução Content Delivery Network (CDN) pela primeira vez, deve ## Requisitos -- Possuir a solução [Content Delivery Network (CDN) da OVH](/links/network/cdn-infrastructure){.external}. +- Possuir a solução [Content Delivery Network (CDN) da OVH](/links/network/cdn-infrastructure). - Ter acesso à gestão da zona DNS do seu nome de domínio. -- Ter acesso à [Área de Cliente OVH](/links/manager){.external}. +- Ter acesso à [Área de Cliente OVH](/links/manager). ## Instruções @@ -22,7 +22,7 @@ Ao configurar a solução Content Delivery Network (CDN) pela primeira vez, deve O primeiro passo desta configuração é a adição de um subdomínio à sua escolha na CDN para que esta última aceite os pedidos HTTP(S) deste domínio. -Para isso, aceda à [Área de Cliente OVH](/links/manager){.external}, na janela `Serviços Dedicados`{.action} selecione a opção `NAS e CDN`{.action}. +Para isso, aceda à [Área de Cliente OVH](/links/manager), na janela `Serviços Dedicados`{.action} selecione a opção `NAS e CDN`{.action}. A seguir, clique em `Adicionar domínio à CDN`{.action}. @@ -102,4 +102,4 @@ Se o domínio responde corretamente no seu serviço web, só terá de editar o c ## Quer saber mais? -Fale com a nossa comunidade de utilizadores em [https://community.ovh.com/en/](https://community.ovh.com/en/){.external} \ No newline at end of file +Fale com a nossa comunidade de utilizadores em [https://community.ovh.com/en/](https://community.ovh.com/en/) \ No newline at end of file diff --git a/pages/network/content_delivery_network_infrastructure/quota/guide.de-de.md b/pages/network/content_delivery_network_infrastructure/quota/guide.de-de.md index bcdd6701ac8..76efdcdbea9 100644 --- a/pages/network/content_delivery_network_infrastructure/quota/guide.de-de.md +++ b/pages/network/content_delivery_network_infrastructure/quota/guide.de-de.md @@ -12,7 +12,7 @@ Mithilfe des Content Delivery Network (CDN) können Sie die Antwortzeiten von We ## Voraussetzungen -- Sie sind in Ihrem [OVHcloud Kundencenter](/links/manager){.external} eingeloggt. +- Sie sind in Ihrem [OVHcloud Kundencenter](/links/manager) eingeloggt. ## Beschreibung @@ -20,11 +20,11 @@ Mithilfe des Content Delivery Network (CDN) können Sie die Antwortzeiten von We Bei der Bestellung erhalten Sie **1 TB** Traffic-Quota. Bitte beachten Sie, dass dieses nicht jeden Monat automatisch erneuert wird. Ist das Quota aufgebraucht (egal über welchen Zeitraum), muss neues Quota bestellt werden. -Wenn Sie zusätzliches Quota benötigen, können Sie dieses direkt über Ihr [OVHcloud Kundencenter](/links/manager){.external} bestellen. +Wenn Sie zusätzliches Quota benötigen, können Sie dieses direkt über Ihr [OVHcloud Kundencenter](/links/manager) bestellen. ![Quota hinzufügen](images/add_quota.png){.thumbnail} -Die Preise für das Quota finden Sie auf der zugehörigen [Webseite](/links/network/cdn-infrastructure){.external}. +Die Preise für das Quota finden Sie auf der zugehörigen [Webseite](/links/network/cdn-infrastructure). Sobald nur noch **100 GB** übrig sind, erhalten Sie eine automatische Warnung zu Ihrem Quota-Verbrauch, damit Sie rechtzeitig weitere Bandbreite bestellen können. Wenn Ihr Quota aufgebraucht ist, wird automatisch die `bypass`-Funktion aktiviert, bis Sie weiteres Quota bestellt haben. diff --git a/pages/network/content_delivery_network_infrastructure/quota/guide.en-gb.md b/pages/network/content_delivery_network_infrastructure/quota/guide.en-gb.md index 64142567bcc..dc0e7906b70 100644 --- a/pages/network/content_delivery_network_infrastructure/quota/guide.en-gb.md +++ b/pages/network/content_delivery_network_infrastructure/quota/guide.en-gb.md @@ -12,7 +12,7 @@ With the Content Delivery Network (CDN), you can optimise your website’s respo ## Requirements -- access to the [OVH Control Panel](/links/manager){.external} +- access to the [OVH Control Panel](/links/manager) ## Instructions @@ -20,11 +20,11 @@ With the Content Delivery Network (CDN), you can optimise your website’s respo When you place an order, it comes with a **1 TB** quota allowance for traffic. It is important to note that this quota is not renewed monthly with your solution. Once you have used up this quota allowance (regardless of duration), you will need to add more quota allowance. -If you need additional quota, you can order it directly via the [OVH Control Panel](/links/manager){.external}: +If you need additional quota, you can order it directly via the [OVH Control Panel](/links/manager): ![Add quota](images/add_quota.png){.thumbnail} -You can view the prices for quota allowance on our [website](/links/network/cdn-infrastructure){.external}. +You can view the prices for quota allowance on our [website](/links/network/cdn-infrastructure). You are automatically notified when you have **100 GB** of quota remaining, so that you have time to order more bandwidth in advance. If you run out of quota allowance, the `bypass` is automatically enabled until you order more quota. diff --git a/pages/network/content_delivery_network_infrastructure/quota/guide.es-es.md b/pages/network/content_delivery_network_infrastructure/quota/guide.es-es.md index 7c9db78d24a..884903e58d6 100644 --- a/pages/network/content_delivery_network_infrastructure/quota/guide.es-es.md +++ b/pages/network/content_delivery_network_infrastructure/quota/guide.es-es.md @@ -14,7 +14,7 @@ Cada conexión al sitio web genera un flujo de datos. Cuando estos datos circula ## Requisitos -- Tener acceso al [área de cliente](/links/manager){.external}. +- Tener acceso al [área de cliente](/links/manager). ## Procedimiento @@ -22,11 +22,11 @@ Cada conexión al sitio web genera un flujo de datos. Cuando estos datos circula Al contratar la solución CDN, puede disfrutar de **1 TB** de tráfico incluido de forma gratuita. Este volumen de tráfico no se renueva cada mes junto con la solución, sino que, una vez consumido (independientemente del plazo), deberá contratar tráfico adicional. -Es posible adquirir tráfico adicional directamente desde el [área de cliente de OVH](/links/manager){.external}. +Es posible adquirir tráfico adicional directamente desde el [área de cliente de OVH](/links/manager). ![Adquirir tráfico](images/add_quota.png){.thumbnail} -Puede consultar el precio de los paquetes de tráfico disponibles en la página de la solución [CDN de OVH](/links/network/cdn-infrastructure){.external}. +Puede consultar el precio de los paquetes de tráfico disponibles en la página de la solución [CDN de OVH](/links/network/cdn-infrastructure). Cuando el tráfico disponible sea inferior a **100 GB**, recibirá una notificación informándole de la necesidad de ampliar el límite de tráfico. Si ha consumido todo el tráfico disponible, la función *bypass* se activará automáticamente hasta que adquiera más tráfico. diff --git a/pages/network/content_delivery_network_infrastructure/quota/guide.fr-fr.md b/pages/network/content_delivery_network_infrastructure/quota/guide.fr-fr.md index f66f4584163..3216e90ab20 100644 --- a/pages/network/content_delivery_network_infrastructure/quota/guide.fr-fr.md +++ b/pages/network/content_delivery_network_infrastructure/quota/guide.fr-fr.md @@ -12,7 +12,7 @@ Le Content Delivery Network (CDN) vous permet d'optimiser le temps de réponse d ## Prérequis -- Avoir accès à votre [espace client OVH](/links/manager){.external}. +- Avoir accès à votre [espace client OVH](/links/manager). ## En pratique @@ -20,11 +20,11 @@ Le Content Delivery Network (CDN) vous permet d'optimiser le temps de réponse d Lors de votre commande, **1 To** de trafic vous est offert. Attention, ce quota n'est pas renouvelé chaque mois avec votre offre. En effet, une fois ce volume consommé (quelle que soit la durée), vous devrez en ajouter à nouveau. -Si vous avez besoin de quota supplémentaire, vous pouvez le commander directement depuis votre [espace client OVH](/links/manager){.external} : +Si vous avez besoin de quota supplémentaire, vous pouvez le commander directement depuis votre [espace client OVH](/links/manager) : ![Ajout de quota](images/add_quota.png){.thumbnail} -Retrouvez les tarifications de ce quota sur [notre site](/links/network/cdn-infrastructure){.external}. +Retrouvez les tarifications de ce quota sur [notre site](/links/network/cdn-infrastructure). Une alerte vous est automatiquement envoyée lorsqu'il vous reste **100 Go** de quota pour que vous puissiez planifier un nouvel achat de bande passante. S'il ne vous reste plus de quota, la fonction `*bypass*` sera automatiquement activée jusqu'à ce que vous possédiez de nouveau du quota disponible. diff --git a/pages/network/content_delivery_network_infrastructure/quota/guide.it-it.md b/pages/network/content_delivery_network_infrastructure/quota/guide.it-it.md index 44cfc563b0f..c1599c057d7 100644 --- a/pages/network/content_delivery_network_infrastructure/quota/guide.it-it.md +++ b/pages/network/content_delivery_network_infrastructure/quota/guide.it-it.md @@ -12,7 +12,7 @@ La CDN (Content Delivery Network) è un servizio che permette di ottimizzare i t ## Prerequisiti -- Avere accesso allo [Spazio Cliente OVH](/links/manager){.external} +- Avere accesso allo [Spazio Cliente OVH](/links/manager) ## Procedura @@ -20,11 +20,11 @@ La CDN (Content Delivery Network) è un servizio che permette di ottimizzare i t L’attivazione della CDN OVH permette di usufruire di **1 TB** di traffico incluso. Questa quota non si rinnova mensilmente con il servizio ma, indipendentemente dalla sua durata, una volta consumata è necessario ordinare una quota aggiuntiva. -Il traffico supplementare può essere aggiunto direttamente dallo [Spazio Cliente OVH](/links/manager){.external}: +Il traffico supplementare può essere aggiunto direttamente dallo [Spazio Cliente OVH](/links/manager): ![Aggiungere quota](images/add_quota.png){.thumbnail} -Le tariffe relative alla quota aggiuntiva sono disponibili sul [sito OVH](/links/network/cdn-infrastructure){.external}. +Le tariffe relative alla quota aggiuntiva sono disponibili sul [sito OVH](/links/network/cdn-infrastructure). Al raggiungimento di **100 GB** residui viene inviata automaticamente una notifica per poter pianificare un nuovo acquisto di banda passante. Se il traffico a disposizione termina si attiva automaticamente la funzione _bypass_, che resterà abilitata fino a quando non sarà nuovamente disponibile una quota. diff --git a/pages/network/content_delivery_network_infrastructure/quota/guide.pl-pl.md b/pages/network/content_delivery_network_infrastructure/quota/guide.pl-pl.md index b3442d0b878..48c94dbbc22 100644 --- a/pages/network/content_delivery_network_infrastructure/quota/guide.pl-pl.md +++ b/pages/network/content_delivery_network_infrastructure/quota/guide.pl-pl.md @@ -12,7 +12,7 @@ CDN (Content Delivery Network) umożliwia optymalizację czasu odpowiedzi Twoich ## Wymagania początkowe -- Dostęp do [Panelu klienta OVH](/links/manager){.external} +- Dostęp do [Panelu klienta OVH](/links/manager) ## W praktyce @@ -20,11 +20,11 @@ CDN (Content Delivery Network) umożliwia optymalizację czasu odpowiedzi Twoich W momencie zamówienia przyznany zostaje Ci limit transferu wynoszący **1 TB**. Pamiętaj, że limit ten **nie jest odnawiany** co miesiąc wraz z odnowieniem Twojej usługi. Po zużyciu całego limitu (niezależnie od czasu, w jakim został on wykorzystany), możesz zamówić nowy pakiet transferu danych. -Jeśli potrzebujesz dodatkowego transferu, możesz zamówić go bezpośrednio w [Panelu klienta](/links/manager){.external}: +Jeśli potrzebujesz dodatkowego transferu, możesz zamówić go bezpośrednio w [Panelu klienta](/links/manager): ![Dodatnie limitu transferu](images/add_quota.png){.thumbnail} -Zapoznaj się z cennikiem pakietów transferu na [stronie WWW OVH](/links/network/cdn-infrastructure){.external}. +Zapoznaj się z cennikiem pakietów transferu na [stronie WWW OVH](/links/network/cdn-infrastructure). W momencie gdy pozostaje Ci **100 GB** z bieżącego limitu transferu, otrzymujesz automatyczne powiadomienie, abyś mógł zaplanować zakup kolejnego pakietu. Jeśli wyczerpałeś cały limit, włączona zostaje automatycznie funkcja `Bypass` do momentu, gdy na Twoim koncie dostępny będzie nowy pakiet transferu danych. diff --git a/pages/network/content_delivery_network_infrastructure/quota/guide.pt-pt.md b/pages/network/content_delivery_network_infrastructure/quota/guide.pt-pt.md index 66f65d12b31..152cf0a368b 100644 --- a/pages/network/content_delivery_network_infrastructure/quota/guide.pt-pt.md +++ b/pages/network/content_delivery_network_infrastructure/quota/guide.pt-pt.md @@ -12,7 +12,7 @@ A solução CDN da OVH permite-lhe otimizar os tempos de resposta dos seus websi ## Requisitos -- Ter acesso à [Área de Cliente OVH](/links/manager){.external}. +- Ter acesso à [Área de Cliente OVH](/links/manager). ## Instruções @@ -20,11 +20,11 @@ A solução CDN da OVH permite-lhe otimizar os tempos de resposta dos seus websi Ao contratar a solução CDN, poderá usufruir de **1 TB** de tráfego incluído. Contudo, este limite não é renovado mensalmente juntamente com a sua solução. Uma vez consumido (independentemente do prazo), deverá renovar o tráfego disponível. -Caso necessite de tráfego adicional, poderá adicionar diretamente a partir da [Área de Cliente OVH](/links/manager){.external}. +Caso necessite de tráfego adicional, poderá adicionar diretamente a partir da [Área de Cliente OVH](/links/manager). ![Adquirir tráfego](images/add_quota.png){.thumbnail} -Pode consultar os preços dos pacotes de tráfego disponíveis no [nosso site](/links/network/cdn-infrastructure){.external}. +Pode consultar os preços dos pacotes de tráfego disponíveis no [nosso site](/links/network/cdn-infrastructure). Quando o tráfego disponível for inferior a **100 GB**, receberá um aviso indicando-lhe que é necessário adquirir mais largura de banda. Se não possuir tráfego na solução, a função `bypass` será automaticamente ativada até que adquira mais largura de banda. @@ -47,4 +47,4 @@ Em ambos os casos, quer os ficheiros estejam guardados na cache ou enviados para ## Quer saber mais? -Fale com a nossa comunidade de utilizadores em [https://community.ovh.com/en/](https://community.ovh.com/en/){.external} \ No newline at end of file +Fale com a nossa comunidade de utilizadores em [https://community.ovh.com/en/](https://community.ovh.com/en/) \ No newline at end of file diff --git a/pages/network/content_delivery_network_infrastructure/ssl_certificate/guide.de-de.md b/pages/network/content_delivery_network_infrastructure/ssl_certificate/guide.de-de.md index f524d653f43..76caebb3fee 100644 --- a/pages/network/content_delivery_network_infrastructure/ssl_certificate/guide.de-de.md +++ b/pages/network/content_delivery_network_infrastructure/ssl_certificate/guide.de-de.md @@ -6,13 +6,13 @@ updated: 2018-02-22 ## Einleitung -Sie können Ihrem Content Delivery Network (CDN) ein [SSL-Zertifikat](/links/web/hosting-options-ssl){.external} hinzufügen, damit Ihre Nutzer auch über das CDN eine gesicherte Verbindung herstellen können. +Sie können Ihrem Content Delivery Network (CDN) ein [SSL-Zertifikat](/links/web/hosting-options-ssl) hinzufügen, damit Ihre Nutzer auch über das CDN eine gesicherte Verbindung herstellen können. **In dieser Anleitung erfahren Sie, wie die SSL-Zertifikate von Let's Encrypt bei OVH funktionieren.** ## Voraussetzungen -- Sie verfügen über ein [CDN von OVH](/links/network/cdn-infrastructure){.external}. +- Sie verfügen über ein [CDN von OVH](/links/network/cdn-infrastructure). - Sie haben Zugriff auf die Verwaltung der DNS-Zone Ihrer Domain. ## Beschreibung @@ -22,7 +22,7 @@ Sie können Ihrem Content Delivery Network (CDN) ein [SSL-Zertifikat](/links/web - Wenn Sie bisher kein Zertifikat konfiguriert haben und Ihre erste Subdomain dem CDN hinzufügen, wird für diese Domain automatisch ein Let's Encrypt-Zertifikat erstellt. - Wenn Sie dem CDN eine weitere Subdomain hinzufügen, wird das Zertifikat automatisch erneuert, damit es auch für die neu eingerichtete Subdomain gilt. -Damit die Zertifikatserstellung erfolgreich ist, muss die neu hinzugefügte Subdomain korrekt auf das CDN zeigen. Hierfür empfehlen wir Ihnen die Anleitung zum Thema „[Erste Konfiguration einer Domain](/pages/network/content_delivery_network_infrastructure/first_domain_name_configuration){.external}“. +Damit die Zertifikatserstellung erfolgreich ist, muss die neu hinzugefügte Subdomain korrekt auf das CDN zeigen. Hierfür empfehlen wir Ihnen die Anleitung zum Thema „[Erste Konfiguration einer Domain](/pages/network/content_delivery_network_infrastructure/first_domain_name_configuration)“. Die Erneuerung des Zertifikats erfolgt automatisch innerhalb von 20 Tagen vor dessen Ablauf. @@ -59,6 +59,6 @@ Wenn das Zertifikat aktiviert ist, erkennen Sie dies am neuen Status: ## Weiterführende Informationen -[Erste Konfiguration einer Domain](/pages/network/content_delivery_network_infrastructure/first_domain_name_configuration){.external} +[Erste Konfiguration einer Domain](/pages/network/content_delivery_network_infrastructure/first_domain_name_configuration) Für den Austausch mit unserer User Community gehen Sie auf . \ No newline at end of file diff --git a/pages/network/content_delivery_network_infrastructure/ssl_certificate/guide.en-gb.md b/pages/network/content_delivery_network_infrastructure/ssl_certificate/guide.en-gb.md index 6b0d95bc3be..1a42ef26495 100644 --- a/pages/network/content_delivery_network_infrastructure/ssl_certificate/guide.en-gb.md +++ b/pages/network/content_delivery_network_infrastructure/ssl_certificate/guide.en-gb.md @@ -6,13 +6,13 @@ updated: 2018-02-22 ## Objective -You can add an [SSL certificate](/links/web/hosting-options-ssl){.external} to your Content Delivery Network (CDN), so that your users can connect securely, even if they do so via the CDN. +You can add an [SSL certificate](/links/web/hosting-options-ssl) to your Content Delivery Network (CDN), so that your users can connect securely, even if they do so via the CDN. **In this guide, we will show you how to do this with a Let's Encrypt certificate, delivered by OVH.** ## Requirements -- an [OVH CDN solution](https://www.ovh.co.uk/cdn/){.external} +- an [OVH CDN solution](https://www.ovh.co.uk/cdn/) - the permissions needed to manage your domain’s DNS zone ## Instructions @@ -22,7 +22,7 @@ You can add an [SSL certificate](/links/web/hosting-options-ssl){.external} to y - If you have not configured any certificates and you are adding your first subdomain to the CDN, a Let's Encrypt certificate will be created automatically for the domain name. - If you are adding another subdomain to the CDN, the certificate will be automatically regenerated to include the new subdomain that you have just added. -To ensure that the certificate is generated properly, the subdomain you add will need to point correctly to the CDN. To check that this is the case, please follow the instructions listed in our guide to [Configuring a domain name for the first time](/pages/network/content_delivery_network_infrastructure/first_domain_name_configuration){.external}. +To ensure that the certificate is generated properly, the subdomain you add will need to point correctly to the CDN. To check that this is the case, please follow the instructions listed in our guide to [Configuring a domain name for the first time](/pages/network/content_delivery_network_infrastructure/first_domain_name_configuration). The certificate is renewed automatically 20 days before its expiry date. @@ -59,6 +59,6 @@ If you already have a Let's Encrypt certificate, then you can use the `Replace w ## Go further -[Configuring a domain name for the first time](/pages/network/content_delivery_network_infrastructure/first_domain_name_configuration){.external} +[Configuring a domain name for the first time](/pages/network/content_delivery_network_infrastructure/first_domain_name_configuration) Join our community of users on . \ No newline at end of file diff --git a/pages/network/content_delivery_network_infrastructure/ssl_certificate/guide.es-es.md b/pages/network/content_delivery_network_infrastructure/ssl_certificate/guide.es-es.md index 5e382797d62..a8af6cbc6d3 100644 --- a/pages/network/content_delivery_network_infrastructure/ssl_certificate/guide.es-es.md +++ b/pages/network/content_delivery_network_infrastructure/ssl_certificate/guide.es-es.md @@ -6,13 +6,13 @@ updated: 2018-02-22 ## Objetivo -Es posible añadir un [certificado SSL](/links/web/hosting-options-ssl){.external} a su red de distribución de contenidos (CDN, del inglés *content delivery network*) para que los usuarios puedan establecer conexiones seguras incluso pasando por la CDN. +Es posible añadir un [certificado SSL](/links/web/hosting-options-ssl) a su red de distribución de contenidos (CDN, del inglés *content delivery network*) para que los usuarios puedan establecer conexiones seguras incluso pasando por la CDN. **Esta guía explica cómo funcionan los certificados SSL Let's Encrypt que ofrece OVH.** ## Requisitos -- Tener contratada la solución [CDN de OVH](/links/network/cdn-infrastructure){.external}. +- Tener contratada la solución [CDN de OVH](/links/network/cdn-infrastructure). - Tener acceso a la gestión de la zona DNS del dominio. ## Procedimiento @@ -22,7 +22,7 @@ Es posible añadir un [certificado SSL](/links/web/hosting-options-ssl){.externa - Si no ha configurado ningún certificado y añade un primer subdominio a la CDN, se generará automáticamente un certificado Let's Encrypt para dicho dominio. - Si añade a la CDN un nuevo subdominio, el certificado se regenerará automáticamente para incluir el subdominio recientemente configurado. -Para poder crear el certificado, es necesario que el subdominio que acaba de añadir apunte correctamente a la CDN. Para más información, consulte nuestra guía sobre cómo [configurar un dominio en la CDN](/pages/network/content_delivery_network_infrastructure/first_domain_name_configuration){.external}. +Para poder crear el certificado, es necesario que el subdominio que acaba de añadir apunte correctamente a la CDN. Para más información, consulte nuestra guía sobre cómo [configurar un dominio en la CDN](/pages/network/content_delivery_network_infrastructure/first_domain_name_configuration). El certificado se renovará automáticamente en los 20 días previos a la expiración del certificado. @@ -59,6 +59,6 @@ Una vez activado el certificado, podrá ver lo siguiente en el área de cliente: ## Más información -[Primera configuración de un dominio](/pages/network/content_delivery_network_infrastructure/first_domain_name_configuration){.external} +[Primera configuración de un dominio](/pages/network/content_delivery_network_infrastructure/first_domain_name_configuration) Interactúe con nuestra comunidad de usuarios en . \ No newline at end of file diff --git a/pages/network/content_delivery_network_infrastructure/ssl_certificate/guide.fr-fr.md b/pages/network/content_delivery_network_infrastructure/ssl_certificate/guide.fr-fr.md index fb81c24dd8c..fe9d9dfc95b 100644 --- a/pages/network/content_delivery_network_infrastructure/ssl_certificate/guide.fr-fr.md +++ b/pages/network/content_delivery_network_infrastructure/ssl_certificate/guide.fr-fr.md @@ -6,13 +6,13 @@ updated: 2018-02-22 ## Objectif -Il est possible d'ajouter un [certificat SSL](/links/web/hosting-options-ssl){.external} à votre offre Content Delivery Network (CDN) afin que vos utilisateurs puissent effectuer des connexions sécurisées, même en passant par le CDN. +Il est possible d'ajouter un [certificat SSL](/links/web/hosting-options-ssl) à votre offre Content Delivery Network (CDN) afin que vos utilisateurs puissent effectuer des connexions sécurisées, même en passant par le CDN. **Dans ce guide, nous allons vous détailler le fonctionnement du SSL Let's Encrypt fourni par OVH.** ## Prérequis -- Posséder l'[offre CDN d'OVH](/links/network/cdn-infrastructure){.external}. +- Posséder l'[offre CDN d'OVH](/links/network/cdn-infrastructure). - Avoir accès à la gestion de la zone DNS de votre domaine. ## En pratique @@ -22,7 +22,7 @@ Il est possible d'ajouter un [certificat SSL](/links/web/hosting-options-ssl){.e - Si vous n'avez configuré aucun certificat et que vous ajoutez votre premier sous-domaine au CDN, un certificat Let's Encrypt sera automatiquement créé pour ce nom de domaine. - Si vous ajoutez un autre sous-domaine au CDN, le certificat sera automatiquement régénéré afin d'y inclure le nouveau sous-domaine que vous venez de configurer. -Pour que la création du certificat se déroule correctement, il est nécessaire que le sous-domaine que vous venez d'ajouter pointe correctement vers le CDN. Pour cela référez-vous au guide vous indiquant comment effectuer une [première configuration d'un nom de domaine](/pages/network/content_delivery_network_infrastructure/first_domain_name_configuration){.external}. +Pour que la création du certificat se déroule correctement, il est nécessaire que le sous-domaine que vous venez d'ajouter pointe correctement vers le CDN. Pour cela référez-vous au guide vous indiquant comment effectuer une [première configuration d'un nom de domaine](/pages/network/content_delivery_network_infrastructure/first_domain_name_configuration). Le renouvellement du certificat est effectué de manière automatique dans les 20 jours précédant l'expiration du certificat. @@ -59,6 +59,6 @@ Une fois le certificat activé, voici ce que vous obtiendrez : ## Aller plus loin -[Première configuration d'un nom de domaine](/pages/network/content_delivery_network_infrastructure/first_domain_name_configuration){.external} +[Première configuration d'un nom de domaine](/pages/network/content_delivery_network_infrastructure/first_domain_name_configuration) Échangez avec notre [communauté d'utilisateurs](/links/community). \ No newline at end of file diff --git a/pages/network/content_delivery_network_infrastructure/ssl_certificate/guide.it-it.md b/pages/network/content_delivery_network_infrastructure/ssl_certificate/guide.it-it.md index 17d328eefb1..464fc91e9a6 100644 --- a/pages/network/content_delivery_network_infrastructure/ssl_certificate/guide.it-it.md +++ b/pages/network/content_delivery_network_infrastructure/ssl_certificate/guide.it-it.md @@ -6,13 +6,13 @@ updated: 2018-02-22 ## Obiettivo -È possibile aggiungere un [certificato SSL](/links/web/hosting-options-ssl){.external} sulla CDN (Content Delivery Network) per consentire agli utenti di stabilire connessioni sicure, anche nei casi in cui il traffico passi attraverso la CDN. +È possibile aggiungere un [certificato SSL](/links/web/hosting-options-ssl) sulla CDN (Content Delivery Network) per consentire agli utenti di stabilire connessioni sicure, anche nei casi in cui il traffico passi attraverso la CDN. **Questa guida ti mostra nel dettaglio il funzionamento del certificato SSL Let's Encrypt fornito da OVH.** ## Prerequisiti -- Disporre della soluzione [CDN OVH](https://www.ovh.it/cdn/){.external} +- Disporre della soluzione [CDN OVH](https://www.ovh.it/cdn/) - Avere accesso alla gestione della zona DNS del dominio ## Procedura diff --git a/pages/network/content_delivery_network_infrastructure/ssl_certificate/guide.pl-pl.md b/pages/network/content_delivery_network_infrastructure/ssl_certificate/guide.pl-pl.md index 437917748b0..e7091ba9c46 100644 --- a/pages/network/content_delivery_network_infrastructure/ssl_certificate/guide.pl-pl.md +++ b/pages/network/content_delivery_network_infrastructure/ssl_certificate/guide.pl-pl.md @@ -6,13 +6,13 @@ updated: 2018-02-22 ## Wprowadzenie -Do Twojej usługi Content Delivery Network (CDN) można dodać [certyfikat SSL](/links/web/hosting-options-ssl){.external}, dzięki czemu Twoi użytkownicy mogą łączyć się bezpiecznie, nawet korzystając z CDN. +Do Twojej usługi Content Delivery Network (CDN) można dodać [certyfikat SSL](/links/web/hosting-options-ssl), dzięki czemu Twoi użytkownicy mogą łączyć się bezpiecznie, nawet korzystając z CDN. **W niniejszym przewodniku wyjaśnimy działanie certyfikatu SSL Let's Encrypt dostarczonego przez OVH.** ## Wymagania początkowe -- Posiadanie [usługi CDN od OVH](/links/network/cdn-infrastructure){.external} +- Posiadanie [usługi CDN od OVH](/links/network/cdn-infrastructure) - Dostęp do interfejsu zarządzania strefą DNS domeny ## W praktyce @@ -22,7 +22,7 @@ Do Twojej usługi Content Delivery Network (CDN) można dodać [certyfikat SSL]( - Jeśli nie skonfigurowałeś żadnego certyfikatu i dodajesz Twoją pierwszą subdomenę do CDN, certyfikat Let's Encrypt zostanie automatycznie utworzony dla tej domeny. - Jeśli dodajesz do CDN kolejną subdomenę, certyfikat zostanie automatycznie odnowiony i obejmie nową, właśnie skonfigurowaną, subdomenę. -Aby tworzenie certyfikatu przebiegało prawidłowo, konieczne jest, aby subdomena, którą właśnie dodałeś, wskazywała poprawnie CDN. Zapoznaj się z przewodnikiem, który wyjaśni, jak przeprowadzić [pierwszą konfigurację domeny](/pages/network/content_delivery_network_infrastructure/first_domain_name_configuration){.external}. +Aby tworzenie certyfikatu przebiegało prawidłowo, konieczne jest, aby subdomena, którą właśnie dodałeś, wskazywała poprawnie CDN. Zapoznaj się z przewodnikiem, który wyjaśni, jak przeprowadzić [pierwszą konfigurację domeny](/pages/network/content_delivery_network_infrastructure/first_domain_name_configuration). Certyfikatu odnawiany jest automatycznie i następuje to w ciągu 20 dni poprzedzających jego wygaśnięcie. @@ -59,6 +59,6 @@ Po aktywacji certyfikatu wyświetli się komunikat: ## Sprawdź również -[Pierwsza konfiguracja domeny](/pages/network/content_delivery_network_infrastructure/first_domain_name_configuration){.external} +[Pierwsza konfiguracja domeny](/pages/network/content_delivery_network_infrastructure/first_domain_name_configuration) Przyłącz się do społeczności naszych użytkowników na stronie . \ No newline at end of file diff --git a/pages/network/content_delivery_network_infrastructure/ssl_certificate/guide.pt-pt.md b/pages/network/content_delivery_network_infrastructure/ssl_certificate/guide.pt-pt.md index 633c088e743..12ffdce1bc3 100644 --- a/pages/network/content_delivery_network_infrastructure/ssl_certificate/guide.pt-pt.md +++ b/pages/network/content_delivery_network_infrastructure/ssl_certificate/guide.pt-pt.md @@ -6,13 +6,13 @@ updated: 2018-02-22 ## Sumário -É possível adicionar um [certificado SSL](https://www.ovh.com/pt/ssl/){.external} na solução CDN (Content Delivery Network) para que os seus utilizadores possam estabelecer ligações seguras, mesmo passando pela CDN. +É possível adicionar um [certificado SSL](https://www.ovh.com/pt/ssl/) na solução CDN (Content Delivery Network) para que os seus utilizadores possam estabelecer ligações seguras, mesmo passando pela CDN. **Este manual explica em detalhes o funcionamento do SSL Let's Encrypt fornecido pela OVH.** ## Requisitos -- Dispor da solução [CDN da OVH](https://www.ovh.com/pt/cdn/){.external}. +- Dispor da solução [CDN da OVH](https://www.ovh.com/pt/cdn/). - Ter acesso à gestão da zona DNS do seu domínio. ## Instruções @@ -22,7 +22,7 @@ updated: 2018-02-22 - Se não configurou nenhum certificado e adicionou o seu primeiro subdomínio à CDN, um certificado Let's Encrypt será automaticamente criado para esse nome de domínio. - Se adicionar outro subdomínio à CDN, o certificado será automaticamente regenerado para incluir o novo subdomínio que configurou. -Para que o certificado seja criado corretamente, é necessário que o subdomínio recentemente adicionado aponte corretamente para a CDN. Para isso, consulte a secção do manual que explica como realizar uma [primeira configuração de um domínio](/pages/network/content_delivery_network_infrastructure/first_domain_name_configuration){.external} (versão em inglês). +Para que o certificado seja criado corretamente, é necessário que o subdomínio recentemente adicionado aponte corretamente para a CDN. Para isso, consulte a secção do manual que explica como realizar uma [primeira configuração de um domínio](/pages/network/content_delivery_network_infrastructure/first_domain_name_configuration) (versão em inglês). A renovação do certificado é realizada automaticamente nos 20 dias antes da expiração do certificado. @@ -59,6 +59,6 @@ Uma vez ativado o certificado, irá obter o seguinte resultado: ## Quer saber mais? -[Primeira configuração de um domínio](/pages/network/content_delivery_network_infrastructure/first_domain_name_configuration){.external} (versão em inglês) +[Primeira configuração de um domínio](/pages/network/content_delivery_network_infrastructure/first_domain_name_configuration) (versão em inglês) -Fale com a nossa comunidade de utilizadores em [https://community.ovh.com/en/](https://community.ovh.com/en/){.external} \ No newline at end of file +Fale com a nossa comunidade de utilizadores em [https://community.ovh.com/en/](https://community.ovh.com/en/) \ No newline at end of file diff --git a/pages/network/load_balancer/case_http2/guide.es-us.md b/pages/network/load_balancer/case_http2/guide.es-us.md index 9b1c30d5682..7b4483877e3 100644 --- a/pages/network/load_balancer/case_http2/guide.es-us.md +++ b/pages/network/load_balancer/case_http2/guide.es-us.md @@ -98,4 +98,4 @@ HTTP/2 200 ## Más información -Interactúe con nuestra comunidad de usuarios en [https://community.ovh.com](https://community.ovh.com){.external}. +Interactúe con nuestra comunidad de usuarios en [https://community.ovh.com](https://community.ovh.com). diff --git a/pages/network/load_balancer/case_http2/guide.fr-ca.md b/pages/network/load_balancer/case_http2/guide.fr-ca.md index 3203d5e1bc4..a3fa5420b9f 100644 --- a/pages/network/load_balancer/case_http2/guide.fr-ca.md +++ b/pages/network/load_balancer/case_http2/guide.fr-ca.md @@ -21,10 +21,10 @@ ALPN (Application-Layer Protocol Negotiation) est une extension TLS qui permet ## Prérequis -- Disposer d'un [Load Balancer OVHcloud](https://www.ovh.com/ca/fr/solutions/load-balancer/){.external}. +- Disposer d'un [Load Balancer OVHcloud](https://www.ovh.com/ca/fr/solutions/load-balancer/). - Un frontend TCP est créé sur le port 443. - Une ferme TCP est créée et des serveurs sont ajoutés. -- Avoir accès à l'[API OVHcloud](/links/api){.external}. +- Avoir accès à l'[API OVHcloud](/links/api). ## En pratique diff --git a/pages/network/load_balancer/case_http2/guide.fr-fr.md b/pages/network/load_balancer/case_http2/guide.fr-fr.md index 0619354ff08..5af1d0250e1 100644 --- a/pages/network/load_balancer/case_http2/guide.fr-fr.md +++ b/pages/network/load_balancer/case_http2/guide.fr-fr.md @@ -21,10 +21,10 @@ ALPN (Application-Layer Protocol Negotiation) est une extension TLS qui permet ## Prérequis -- Disposer d'un [Load Balancer OVHcloud](/links/network/load-balancer){.external} (Pack 2 minimum). +- Disposer d'un [Load Balancer OVHcloud](/links/network/load-balancer) (Pack 2 minimum). - Un frontend TCP créé sur le port 443. - Une ferme TCP créée et des serveurs ajoutés. -- Avoir accès à l'[API OVHcloud](/links/api){.external}. +- Avoir accès à l'[API OVHcloud](/links/api). ## En pratique diff --git a/pages/network/load_balancer/case_http2/guide.it-it.md b/pages/network/load_balancer/case_http2/guide.it-it.md index b43261c47a2..0c0c2610599 100644 --- a/pages/network/load_balancer/case_http2/guide.it-it.md +++ b/pages/network/load_balancer/case_http2/guide.it-it.md @@ -21,10 +21,10 @@ L’ALPN (Application-Layer Protocol Negotiation) è un'estensione TLS che conse ## Prerequisiti -- Disporre di un [Load Balancer OVH](https://www.ovh.it/soluzioni/load-balancer/){.external} +- Disporre di un [Load Balancer OVH](https://www.ovh.it/soluzioni/load-balancer/) - Aver creato un front-end TCP - Aver creato una farm TCP e aver aggiunto i server -- Avere accesso allo [Spazio Cliente OVH](/links/manager){.external} +- Avere accesso allo [Spazio Cliente OVH](/links/manager) ## Procedura diff --git a/pages/network/load_balancer/create_balancing/guide.de-de.md b/pages/network/load_balancer/create_balancing/guide.de-de.md index 6fe2c8985a5..3b904017b58 100644 --- a/pages/network/load_balancer/create_balancing/guide.de-de.md +++ b/pages/network/load_balancer/create_balancing/guide.de-de.md @@ -12,7 +12,7 @@ Der neue OVH Loadbalancer bietet Ihnen mehrere Lastverteilungstypen für Ihre Di ## Voraussetzungen -- Sie sind in Ihrem [OVHcloud Kundencenter](/links/manager){.external} eingeloggt. +- Sie sind in Ihrem [OVHcloud Kundencenter](/links/manager) eingeloggt. - Sie haben eine Serverfarm erstellt. ## Beschreibung @@ -21,7 +21,7 @@ Der neue OVH Loadbalancer bietet Ihnen mehrere Lastverteilungstypen für Ihre Di Lastverteilung (engl. „Load Balancing“) wird in Serverfarmen verwendet. Diese Einstellung bestimmt, wie Anfragen zwischen den verschiedenen Servern einer Farm aufgeteilt werden. -Weitere Informationen zu den Grundbestandteilen des OVH Loadbalancers finden Sie in der [Einführung zum OVH Loadbalancer](/pages/network/load_balancer/use_presentation){.external}. +Weitere Informationen zu den Grundbestandteilen des OVH Loadbalancers finden Sie in der [Einführung zum OVH Loadbalancer](/pages/network/load_balancer/use_presentation). |Algorithmus|Funktion| |---|---| diff --git a/pages/network/load_balancer/create_balancing/guide.en-asia.md b/pages/network/load_balancer/create_balancing/guide.en-asia.md index c36f003bce4..0d25c0f0aea 100644 --- a/pages/network/load_balancer/create_balancing/guide.en-asia.md +++ b/pages/network/load_balancer/create_balancing/guide.en-asia.md @@ -21,7 +21,7 @@ The new OVH Load Balancer service offers a variety of load balancing methods for Load balancing is used in server farms. This setting defines the way that requests are distributed between the servers within the farm. -To understand the basics of the OVH Load Balancer service, please refer to the [Load Balancer Introduction](/pages/network/load_balancer/use_presentation){.external}. +To understand the basics of the OVH Load Balancer service, please refer to the [Load Balancer Introduction](/pages/network/load_balancer/use_presentation). |Algorithm|Features| |---|---| diff --git a/pages/network/load_balancer/create_balancing/guide.en-au.md b/pages/network/load_balancer/create_balancing/guide.en-au.md index c36f003bce4..0d25c0f0aea 100644 --- a/pages/network/load_balancer/create_balancing/guide.en-au.md +++ b/pages/network/load_balancer/create_balancing/guide.en-au.md @@ -21,7 +21,7 @@ The new OVH Load Balancer service offers a variety of load balancing methods for Load balancing is used in server farms. This setting defines the way that requests are distributed between the servers within the farm. -To understand the basics of the OVH Load Balancer service, please refer to the [Load Balancer Introduction](/pages/network/load_balancer/use_presentation){.external}. +To understand the basics of the OVH Load Balancer service, please refer to the [Load Balancer Introduction](/pages/network/load_balancer/use_presentation). |Algorithm|Features| |---|---| diff --git a/pages/network/load_balancer/create_balancing/guide.en-ca.md b/pages/network/load_balancer/create_balancing/guide.en-ca.md index c36f003bce4..0d25c0f0aea 100644 --- a/pages/network/load_balancer/create_balancing/guide.en-ca.md +++ b/pages/network/load_balancer/create_balancing/guide.en-ca.md @@ -21,7 +21,7 @@ The new OVH Load Balancer service offers a variety of load balancing methods for Load balancing is used in server farms. This setting defines the way that requests are distributed between the servers within the farm. -To understand the basics of the OVH Load Balancer service, please refer to the [Load Balancer Introduction](/pages/network/load_balancer/use_presentation){.external}. +To understand the basics of the OVH Load Balancer service, please refer to the [Load Balancer Introduction](/pages/network/load_balancer/use_presentation). |Algorithm|Features| |---|---| diff --git a/pages/network/load_balancer/create_balancing/guide.en-gb.md b/pages/network/load_balancer/create_balancing/guide.en-gb.md index c36f003bce4..0d25c0f0aea 100644 --- a/pages/network/load_balancer/create_balancing/guide.en-gb.md +++ b/pages/network/load_balancer/create_balancing/guide.en-gb.md @@ -21,7 +21,7 @@ The new OVH Load Balancer service offers a variety of load balancing methods for Load balancing is used in server farms. This setting defines the way that requests are distributed between the servers within the farm. -To understand the basics of the OVH Load Balancer service, please refer to the [Load Balancer Introduction](/pages/network/load_balancer/use_presentation){.external}. +To understand the basics of the OVH Load Balancer service, please refer to the [Load Balancer Introduction](/pages/network/load_balancer/use_presentation). |Algorithm|Features| |---|---| diff --git a/pages/network/load_balancer/create_balancing/guide.en-sg.md b/pages/network/load_balancer/create_balancing/guide.en-sg.md index c36f003bce4..0d25c0f0aea 100644 --- a/pages/network/load_balancer/create_balancing/guide.en-sg.md +++ b/pages/network/load_balancer/create_balancing/guide.en-sg.md @@ -21,7 +21,7 @@ The new OVH Load Balancer service offers a variety of load balancing methods for Load balancing is used in server farms. This setting defines the way that requests are distributed between the servers within the farm. -To understand the basics of the OVH Load Balancer service, please refer to the [Load Balancer Introduction](/pages/network/load_balancer/use_presentation){.external}. +To understand the basics of the OVH Load Balancer service, please refer to the [Load Balancer Introduction](/pages/network/load_balancer/use_presentation). |Algorithm|Features| |---|---| diff --git a/pages/network/load_balancer/create_balancing/guide.es-es.md b/pages/network/load_balancer/create_balancing/guide.es-es.md index b91ac70256b..a8e597376be 100644 --- a/pages/network/load_balancer/create_balancing/guide.es-es.md +++ b/pages/network/load_balancer/create_balancing/guide.es-es.md @@ -12,7 +12,7 @@ El nuevo Load Balancer de OVH ofrece distintos tipos de balanceo de la carga de ## Requisitos -- Estar conectado al [área de cliente de OVH](/links/manager){.external}. +- Estar conectado al [área de cliente de OVH](/links/manager). - Haber creado una granja de servidores. ## Procedimiento @@ -21,7 +21,7 @@ El nuevo Load Balancer de OVH ofrece distintos tipos de balanceo de la carga de En las granjas de servidores, el balanceo de carga determina la forma en la que las peticiones se distribuirán entre los distintos servidores de la granja. -Para conocer las principales características del Load Balancer de OVH, consulte la [guía de presentación del servicio](/pages/network/load_balancer/use_presentation){.external}. +Para conocer las principales características del Load Balancer de OVH, consulte la [guía de presentación del servicio](/pages/network/load_balancer/use_presentation). |Algoritmo|Funcionalidades| |---|---| diff --git a/pages/network/load_balancer/create_balancing/guide.es-us.md b/pages/network/load_balancer/create_balancing/guide.es-us.md index b91ac70256b..a8e597376be 100644 --- a/pages/network/load_balancer/create_balancing/guide.es-us.md +++ b/pages/network/load_balancer/create_balancing/guide.es-us.md @@ -12,7 +12,7 @@ El nuevo Load Balancer de OVH ofrece distintos tipos de balanceo de la carga de ## Requisitos -- Estar conectado al [área de cliente de OVH](/links/manager){.external}. +- Estar conectado al [área de cliente de OVH](/links/manager). - Haber creado una granja de servidores. ## Procedimiento @@ -21,7 +21,7 @@ El nuevo Load Balancer de OVH ofrece distintos tipos de balanceo de la carga de En las granjas de servidores, el balanceo de carga determina la forma en la que las peticiones se distribuirán entre los distintos servidores de la granja. -Para conocer las principales características del Load Balancer de OVH, consulte la [guía de presentación del servicio](/pages/network/load_balancer/use_presentation){.external}. +Para conocer las principales características del Load Balancer de OVH, consulte la [guía de presentación del servicio](/pages/network/load_balancer/use_presentation). |Algoritmo|Funcionalidades| |---|---| diff --git a/pages/network/load_balancer/create_balancing/guide.fr-ca.md b/pages/network/load_balancer/create_balancing/guide.fr-ca.md index 982e3197303..2f5e1657ebf 100644 --- a/pages/network/load_balancer/create_balancing/guide.fr-ca.md +++ b/pages/network/load_balancer/create_balancing/guide.fr-ca.md @@ -21,7 +21,7 @@ Le nouveau service OVH Load Balancer offre différents types de répartition de La répartition de charge est utilisée dans les fermes de serveurs. C'est ce paramètre qui définit la manière dont les requêtes sont réparties entre les serveurs de la ferme. -Pour connaître les différentes parties élémentaires du service OVH Load Balancer, voir [Présentation Load Balancer](/pages/network/load_balancer/use_presentation){.external}. +Pour connaître les différentes parties élémentaires du service OVH Load Balancer, voir [Présentation Load Balancer](/pages/network/load_balancer/use_presentation). |Algorithme|Fonctionnalités| |---|---| diff --git a/pages/network/load_balancer/create_balancing/guide.fr-fr.md b/pages/network/load_balancer/create_balancing/guide.fr-fr.md index 6741f42e175..5ba2fa28b7f 100644 --- a/pages/network/load_balancer/create_balancing/guide.fr-fr.md +++ b/pages/network/load_balancer/create_balancing/guide.fr-fr.md @@ -22,7 +22,7 @@ Le service OVHcloud Load Balancer offre différents types de répartition de cha La répartition de charge est utilisée dans les fermes de serveurs. C'est ce paramètre qui définit la manière dont les requêtes sont réparties entre les serveurs de la ferme. -Pour connaître les différentes parties élémentaires du service OVHcloud Load Balancer, consultez la [présentation du Load Balancer](/pages/network/load_balancer/use_presentation){.external}. +Pour connaître les différentes parties élémentaires du service OVHcloud Load Balancer, consultez la [présentation du Load Balancer](/pages/network/load_balancer/use_presentation). |Algorithme|Fonctionnalités| |---|---| diff --git a/pages/network/load_balancer/create_balancing/guide.it-it.md b/pages/network/load_balancer/create_balancing/guide.it-it.md index 41e0d7ac0ac..9d94c5e9bf3 100644 --- a/pages/network/load_balancer/create_balancing/guide.it-it.md +++ b/pages/network/load_balancer/create_balancing/guide.it-it.md @@ -21,7 +21,7 @@ La nuova soluzione OVH Load Balancer offre diverse tipologie di ripartizione del La ripartizione del carico si utilizza nelle server farm. Attraverso questo parametro si definisce il modo in cui le richieste vengono suddivise tra i server della farm. -Per saperne di più sul servizio OVH Load Balancer, consulta la seguente guida: [Presentazione Load Balancer](/pages/network/load_balancer/use_presentation){.external}. +Per saperne di più sul servizio OVH Load Balancer, consulta la seguente guida: [Presentazione Load Balancer](/pages/network/load_balancer/use_presentation). |Algoritmo|Caratteristiche| |---|---| diff --git a/pages/network/load_balancer/create_balancing/guide.pl-pl.md b/pages/network/load_balancer/create_balancing/guide.pl-pl.md index 55b097af757..cc922e077b2 100644 --- a/pages/network/load_balancer/create_balancing/guide.pl-pl.md +++ b/pages/network/load_balancer/create_balancing/guide.pl-pl.md @@ -12,7 +12,7 @@ Nowa usługa Load Balancer oferuje różne typy równoważenia obciążenia (loa ## Wymagania początkowe -- Dostęp do [Panelu klienta OVH](/links/manager){.external} +- Dostęp do [Panelu klienta OVH](/links/manager) - Aktywna usługa Load Balancer - Utworzona farma serwerów @@ -22,7 +22,7 @@ Nowa usługa Load Balancer oferuje różne typy równoważenia obciążenia (loa Równoważenie obciążenia realizowane jest w farmach serwerów. Poniżej podane są parametry, które określają sposób, w jaki zapytania są rozdzielane między serwery danej farmy. -Poznaj podstawowe części składowe usługi w [przewodniku prezentującym Load Balancer](/pages/network/load_balancer/use_presentation){.external}. +Poznaj podstawowe części składowe usługi w [przewodniku prezentującym Load Balancer](/pages/network/load_balancer/use_presentation). |Algorytm|Funkcje| |---|---| diff --git a/pages/network/load_balancer/create_balancing/guide.pt-pt.md b/pages/network/load_balancer/create_balancing/guide.pt-pt.md index c1843a01d3c..d5af737a31b 100644 --- a/pages/network/load_balancer/create_balancing/guide.pt-pt.md +++ b/pages/network/load_balancer/create_balancing/guide.pt-pt.md @@ -12,7 +12,7 @@ O novo Load Balancer OVH oferece diferentes tipos de repartição de carga para ## Requisitos -- Ter acesso à [Área de Cliente OVH](/links/manager){.external}. +- Ter acesso à [Área de Cliente OVH](/links/manager). - Ter uma Farm de servidores criada. ## Instruções @@ -21,7 +21,7 @@ O novo Load Balancer OVH oferece diferentes tipos de repartição de carga para A repartição de carga é utilizada nas Farms de servidores. É este parâmetro que define a forma como os pedidos são distribuídos entre os servidores da Farm. -Para conhecer os principais elementos do Load Balancer OVH, consulte [Apresentação do Load Balancer](/pages/network/load_balancer/use_presentation){.external}. +Para conhecer os principais elementos do Load Balancer OVH, consulte [Apresentação do Load Balancer](/pages/network/load_balancer/use_presentation). |Algoritmo|Funcionalidades| |---|---| diff --git a/pages/network/load_balancer/create_probes/guide.en-asia.md b/pages/network/load_balancer/create_probes/guide.en-asia.md index cebe6b13d2f..52be1704be5 100644 --- a/pages/network/load_balancer/create_probes/guide.en-asia.md +++ b/pages/network/load_balancer/create_probes/guide.en-asia.md @@ -83,7 +83,7 @@ All other probe fields can keep their default values. Just apply the configurati By default, the HTTP `probe` sends an "OPTIONS" request on "/" in HTTP/1.0, without a domain name. In many cases, this is sufficient, but some servers do not manage this method. You can carry out much more powerful tests with the HTTP probe. For example, a good practice when exposing a HTTP service is to add a router dedicated to probes. It is normal to see "/status", "/health", and "/check", which summarise the service’s status. -In practice, if you want to configure the probe to send a "GET" request on [http://api.example.com/status](http://api.example.com/status){.external}, it gives: +In practice, if you want to configure the probe to send a "GET" request on [http://api.example.com/status](http://api.example.com/status), it gives: |Field|Value and description| |---|---| @@ -91,7 +91,7 @@ In practice, if you want to configure the probe to send a "GET" request on [http |farmId|Your TCP or HTTP farm| |probe.type|http| |probe.method|GET| -|probe.url|[http://api.example.com/status](http://api.example.com/status){.external}| +|probe.url|[http://api.example.com/status](http://api.example.com/status)| |probe.match|status| |probe.pattern|200 (multiple status codes can be added, provided they are separated by commas)| diff --git a/pages/network/load_balancer/create_probes/guide.en-au.md b/pages/network/load_balancer/create_probes/guide.en-au.md index cebe6b13d2f..52be1704be5 100644 --- a/pages/network/load_balancer/create_probes/guide.en-au.md +++ b/pages/network/load_balancer/create_probes/guide.en-au.md @@ -83,7 +83,7 @@ All other probe fields can keep their default values. Just apply the configurati By default, the HTTP `probe` sends an "OPTIONS" request on "/" in HTTP/1.0, without a domain name. In many cases, this is sufficient, but some servers do not manage this method. You can carry out much more powerful tests with the HTTP probe. For example, a good practice when exposing a HTTP service is to add a router dedicated to probes. It is normal to see "/status", "/health", and "/check", which summarise the service’s status. -In practice, if you want to configure the probe to send a "GET" request on [http://api.example.com/status](http://api.example.com/status){.external}, it gives: +In practice, if you want to configure the probe to send a "GET" request on [http://api.example.com/status](http://api.example.com/status), it gives: |Field|Value and description| |---|---| @@ -91,7 +91,7 @@ In practice, if you want to configure the probe to send a "GET" request on [http |farmId|Your TCP or HTTP farm| |probe.type|http| |probe.method|GET| -|probe.url|[http://api.example.com/status](http://api.example.com/status){.external}| +|probe.url|[http://api.example.com/status](http://api.example.com/status)| |probe.match|status| |probe.pattern|200 (multiple status codes can be added, provided they are separated by commas)| diff --git a/pages/network/load_balancer/create_probes/guide.en-ca.md b/pages/network/load_balancer/create_probes/guide.en-ca.md index cebe6b13d2f..52be1704be5 100644 --- a/pages/network/load_balancer/create_probes/guide.en-ca.md +++ b/pages/network/load_balancer/create_probes/guide.en-ca.md @@ -83,7 +83,7 @@ All other probe fields can keep their default values. Just apply the configurati By default, the HTTP `probe` sends an "OPTIONS" request on "/" in HTTP/1.0, without a domain name. In many cases, this is sufficient, but some servers do not manage this method. You can carry out much more powerful tests with the HTTP probe. For example, a good practice when exposing a HTTP service is to add a router dedicated to probes. It is normal to see "/status", "/health", and "/check", which summarise the service’s status. -In practice, if you want to configure the probe to send a "GET" request on [http://api.example.com/status](http://api.example.com/status){.external}, it gives: +In practice, if you want to configure the probe to send a "GET" request on [http://api.example.com/status](http://api.example.com/status), it gives: |Field|Value and description| |---|---| @@ -91,7 +91,7 @@ In practice, if you want to configure the probe to send a "GET" request on [http |farmId|Your TCP or HTTP farm| |probe.type|http| |probe.method|GET| -|probe.url|[http://api.example.com/status](http://api.example.com/status){.external}| +|probe.url|[http://api.example.com/status](http://api.example.com/status)| |probe.match|status| |probe.pattern|200 (multiple status codes can be added, provided they are separated by commas)| diff --git a/pages/network/load_balancer/create_probes/guide.en-gb.md b/pages/network/load_balancer/create_probes/guide.en-gb.md index cebe6b13d2f..52be1704be5 100644 --- a/pages/network/load_balancer/create_probes/guide.en-gb.md +++ b/pages/network/load_balancer/create_probes/guide.en-gb.md @@ -83,7 +83,7 @@ All other probe fields can keep their default values. Just apply the configurati By default, the HTTP `probe` sends an "OPTIONS" request on "/" in HTTP/1.0, without a domain name. In many cases, this is sufficient, but some servers do not manage this method. You can carry out much more powerful tests with the HTTP probe. For example, a good practice when exposing a HTTP service is to add a router dedicated to probes. It is normal to see "/status", "/health", and "/check", which summarise the service’s status. -In practice, if you want to configure the probe to send a "GET" request on [http://api.example.com/status](http://api.example.com/status){.external}, it gives: +In practice, if you want to configure the probe to send a "GET" request on [http://api.example.com/status](http://api.example.com/status), it gives: |Field|Value and description| |---|---| @@ -91,7 +91,7 @@ In practice, if you want to configure the probe to send a "GET" request on [http |farmId|Your TCP or HTTP farm| |probe.type|http| |probe.method|GET| -|probe.url|[http://api.example.com/status](http://api.example.com/status){.external}| +|probe.url|[http://api.example.com/status](http://api.example.com/status)| |probe.match|status| |probe.pattern|200 (multiple status codes can be added, provided they are separated by commas)| diff --git a/pages/network/load_balancer/create_probes/guide.en-sg.md b/pages/network/load_balancer/create_probes/guide.en-sg.md index cebe6b13d2f..52be1704be5 100644 --- a/pages/network/load_balancer/create_probes/guide.en-sg.md +++ b/pages/network/load_balancer/create_probes/guide.en-sg.md @@ -83,7 +83,7 @@ All other probe fields can keep their default values. Just apply the configurati By default, the HTTP `probe` sends an "OPTIONS" request on "/" in HTTP/1.0, without a domain name. In many cases, this is sufficient, but some servers do not manage this method. You can carry out much more powerful tests with the HTTP probe. For example, a good practice when exposing a HTTP service is to add a router dedicated to probes. It is normal to see "/status", "/health", and "/check", which summarise the service’s status. -In practice, if you want to configure the probe to send a "GET" request on [http://api.example.com/status](http://api.example.com/status){.external}, it gives: +In practice, if you want to configure the probe to send a "GET" request on [http://api.example.com/status](http://api.example.com/status), it gives: |Field|Value and description| |---|---| @@ -91,7 +91,7 @@ In practice, if you want to configure the probe to send a "GET" request on [http |farmId|Your TCP or HTTP farm| |probe.type|http| |probe.method|GET| -|probe.url|[http://api.example.com/status](http://api.example.com/status){.external}| +|probe.url|[http://api.example.com/status](http://api.example.com/status)| |probe.match|status| |probe.pattern|200 (multiple status codes can be added, provided they are separated by commas)| diff --git a/pages/network/load_balancer/create_probes/guide.en-us.md b/pages/network/load_balancer/create_probes/guide.en-us.md index cebe6b13d2f..52be1704be5 100644 --- a/pages/network/load_balancer/create_probes/guide.en-us.md +++ b/pages/network/load_balancer/create_probes/guide.en-us.md @@ -83,7 +83,7 @@ All other probe fields can keep their default values. Just apply the configurati By default, the HTTP `probe` sends an "OPTIONS" request on "/" in HTTP/1.0, without a domain name. In many cases, this is sufficient, but some servers do not manage this method. You can carry out much more powerful tests with the HTTP probe. For example, a good practice when exposing a HTTP service is to add a router dedicated to probes. It is normal to see "/status", "/health", and "/check", which summarise the service’s status. -In practice, if you want to configure the probe to send a "GET" request on [http://api.example.com/status](http://api.example.com/status){.external}, it gives: +In practice, if you want to configure the probe to send a "GET" request on [http://api.example.com/status](http://api.example.com/status), it gives: |Field|Value and description| |---|---| @@ -91,7 +91,7 @@ In practice, if you want to configure the probe to send a "GET" request on [http |farmId|Your TCP or HTTP farm| |probe.type|http| |probe.method|GET| -|probe.url|[http://api.example.com/status](http://api.example.com/status){.external}| +|probe.url|[http://api.example.com/status](http://api.example.com/status)| |probe.match|status| |probe.pattern|200 (multiple status codes can be added, provided they are separated by commas)| diff --git a/pages/network/load_balancer/create_probes/guide.fr-ca.md b/pages/network/load_balancer/create_probes/guide.fr-ca.md index 6f386f10f84..cd48aa0bb0b 100644 --- a/pages/network/load_balancer/create_probes/guide.fr-ca.md +++ b/pages/network/load_balancer/create_probes/guide.fr-ca.md @@ -83,7 +83,7 @@ Tous les autres champs probe peuvent rester à leur valeur par défaut. Il ne re Par défaut, la `sonde` HTTP envoie une requête "OPTIONS" sur "/" en HTTP/1.0, sans nom de domaine. Cela suffit dans beaucoup de cas, mais certains serveurs ne gèrent pas cette méthode. Et il est possible de faire des tests beaucoup plus puissants avec la sonde HTTP. Par exemple, une bonne pratique lors de l'exposition d'un service HTTP consiste à ajouter une route dédiée aux sondes. Il est courant de retrouver des "/status", "/health", "/check" qui renvoient une synthèse de l'état du service. -Dans la pratique, si vous voulez configurer la sonde pour envoyer une requête "GET" sur [http://api.example.com/status](http://api.example.com/status){.external}, cela donne : +Dans la pratique, si vous voulez configurer la sonde pour envoyer une requête "GET" sur [http://api.example.com/status](http://api.example.com/status), cela donne : |Champ|Valeur et description| |---|---| @@ -91,7 +91,7 @@ Dans la pratique, si vous voulez configurer la sonde pour envoyer une requête " |farmId|Identifiant de votre ferme TCP ou HTTP| |probe.type|http| |probe.method|GET| -|probe.url|[http://api.example.com/status](http://api.example.com/status){.external}| +|probe.url|[http://api.example.com/status](http://api.example.com/status)| |probe.match|status| |probe.pattern|200 (Plusieurs codes d'état peuvent être ajoutés, en les séparant par des virgules)| diff --git a/pages/network/load_balancer/create_probes/guide.fr-fr.md b/pages/network/load_balancer/create_probes/guide.fr-fr.md index 2508fd55185..0dda6298009 100644 --- a/pages/network/load_balancer/create_probes/guide.fr-fr.md +++ b/pages/network/load_balancer/create_probes/guide.fr-fr.md @@ -86,7 +86,7 @@ Tous les autres champs probe peuvent rester à leur valeur par défaut. Il ne re Par défaut, la sonde HTTP envoie une requête `OPTIONS` sur `/` en HTTP/1.0, sans nom de domaine. Cela suffit dans beaucoup de cas, mais certains serveurs ne gèrent pas cette méthode.
Il est possible de faire des tests beaucoup plus puissants avec la sonde HTTP. Par exemple, une bonne pratique lors de l'exposition d'un service HTTP consiste à ajouter une route dédiée aux sondes. Il est courant de retrouver des `/status`, `/health`, `/check` qui renvoient une synthèse de l'état du service. -Dans la pratique, si vous voulez configurer la sonde pour envoyer une requête `GET` sur [http://api.example.com/status](http://api.example.com/status){.external}, cela donne : +Dans la pratique, si vous voulez configurer la sonde pour envoyer une requête `GET` sur [http://api.example.com/status](http://api.example.com/status), cela donne : |Champ|Valeur et description| |---|---| @@ -94,7 +94,7 @@ Dans la pratique, si vous voulez configurer la sonde pour envoyer une requête ` |farmId|Identifiant de votre ferme TCP ou HTTP| |probe.type|http| |probe.method|GET| -|probe.url|[http://api.example.com/status](http://api.example.com/status){.external}| +|probe.url|[http://api.example.com/status](http://api.example.com/status)| |probe.match|status| |probe.pattern|200 (plusieurs codes d'état peuvent être ajoutés, en les séparant par des virgules)| diff --git a/pages/network/load_balancer/create_proxyprotocol/guide.en-gb.md b/pages/network/load_balancer/create_proxyprotocol/guide.en-gb.md index b86b71fbb4d..4de31950a93 100644 --- a/pages/network/load_balancer/create_proxyprotocol/guide.en-gb.md +++ b/pages/network/load_balancer/create_proxyprotocol/guide.en-gb.md @@ -57,7 +57,7 @@ The list of IPv4 outbound addresses potentially used by your OVHcloud Load Balan ### Introduction to ProxyProtocol -ProxyProtocol was developed by the [HAProxy](http://haproxy.org/){.external} Load Balancer team as the TCP counterpart to standard HTTP headers like X-Forwarded-For. It was designed to forward at minimum: +ProxyProtocol was developed by the [HAProxy](http://haproxy.org/) Load Balancer team as the TCP counterpart to standard HTTP headers like X-Forwarded-For. It was designed to forward at minimum: - the L4 protocol name used (TCP4 for IPv4 or TCP6 for IPv6); - the source IPv4 or IPv6 address; @@ -72,7 +72,7 @@ Indeed, this protocol exists in 2 versions: Version 1 is largely sufficient for most uses (although less optimized) and is often the only version supported by compatible software. Version 2, being a binary format, is faster to parse. It also adds the ability to indicate whether the original connection was encrypted (the equivalent of the X-Forwarded-Proto header) as well as the domain specified in the Common Name field of the certificate used, if applicable. -To learn more about ProxyProtocol, please consult the [ProxyProtocol specification](http://www.haproxy.org/download/1.8/doc/proxy-protocol.txt){.external}. +To learn more about ProxyProtocol, please consult the [ProxyProtocol specification](http://www.haproxy.org/download/1.8/doc/proxy-protocol.txt). ### Activating ProxyProtocol for one of your servers @@ -156,11 +156,11 @@ service nginx reload > This example uses the HTTP protocol for more simplicity. If you are using HTTP, we strongly recommend using HTTP headers instead of ProxyProtocol, unless your OVHcloud Load Balancer service is configured in TCP. This can happen in the case of SSL termination for HTTP/2, for example. > -For more information on configuring ProxyProtocol in Nginx, please consult [the project's official documentation](https://www.nginx.com/resources/admin-guide/proxy-protocol/){.external}. +For more information on configuring ProxyProtocol in Nginx, please consult [the project's official documentation](https://www.nginx.com/resources/admin-guide/proxy-protocol/). #### Apache -The management of ProxyProtocol in Apache is still young. An unofficial implementation compatible with Apache 2.4 is available on Github ([https://github.com/roadrunner2/mod-proxy-protocol](https://github.com/roadrunner2/mod-proxy-protocol){.external}) but has not been maintained since 2014. An official implementation is found in the `mod_remoteip` module which is also used to manage headers from the X-Forwarded-For family. +The management of ProxyProtocol in Apache is still young. An unofficial implementation compatible with Apache 2.4 is available on Github ([https://github.com/roadrunner2/mod-proxy-protocol](https://github.com/roadrunner2/mod-proxy-protocol)) but has not been maintained since 2014. An official implementation is found in the `mod_remoteip` module which is also used to manage headers from the X-Forwarded-For family. `mod-proxy-protocol` supports ProxyProtocol versions 1 and 2. However, it does not allow specifying a list of source IP addresses authorized to use ProxyProtocol, although this is mentioned in the module's projects. @@ -208,7 +208,7 @@ sudo apxs -i -a -c mod_proxy_protocol.c service apache2 restart ``` -To learn more about configuring the `mod-proxy-protocol` module, please consult [its documentation](http://roadrunner2.github.io/mod-proxy-protocol/mod_proxy_protocol.html){.external}. +To learn more about configuring the `mod-proxy-protocol` module, please consult [its documentation](http://roadrunner2.github.io/mod-proxy-protocol/mod_proxy_protocol.html). ##### **With mod_remoteip** @@ -233,7 +233,7 @@ a2enmod remoteip service apache2 restart ``` -To learn more about configuring the `mod_remoteip` module, please consult [its documentation](https://httpd.apache.org/docs/trunk/mod/mod_remoteip.html#remoteipproxyprotocol){.external}. +To learn more about configuring the `mod_remoteip` module, please consult [its documentation](https://httpd.apache.org/docs/trunk/mod/mod_remoteip.html#remoteipproxyprotocol). #### HAProxy diff --git a/pages/network/load_balancer/create_proxyprotocol/guide.fr-ca.md b/pages/network/load_balancer/create_proxyprotocol/guide.fr-ca.md index 7d12b07732d..f9e28324e23 100644 --- a/pages/network/load_balancer/create_proxyprotocol/guide.fr-ca.md +++ b/pages/network/load_balancer/create_proxyprotocol/guide.fr-ca.md @@ -43,7 +43,7 @@ La liste des IPv4 de sortie potentiellement utilisées par votre service OVH Loa > ## Presentation du ProxyProtocol -Le ProxyProtocol a été développé par l'équipe du Load Balancer [HAPRoxy](http://haproxy.org/){.external} comme l'homologue en TCP des En-Têtes HTTP standards telles que X-Forwarded-For. Il a été pensé pour faire suivre au minimum : +Le ProxyProtocol a été développé par l'équipe du Load Balancer [HAPRoxy](http://haproxy.org/) comme l'homologue en TCP des En-Têtes HTTP standards telles que X-Forwarded-For. Il a été pensé pour faire suivre au minimum : - le nom du protocole L4 utilisé (TCP4 pour l'IPv4 ou TCP6 pour l'IPv6) ; - l'adresse IPv4 ou IPv6 source ; @@ -55,7 +55,7 @@ En effet, ce protocole existe en 2 versions: - La version 1, au format texte - L La version 1 étant largement suffisante pour la plupart des usages (bien que moins optimisée), elle est souvent la seule version gérée par les logiciels compatibles. La version 2 étant un format binaire, est plus rapide à analyser. Elle ajoute également la possibilité d'indiquer si la connexion d'origine était chiffrée (l'équivalent de l'En-Tête X-Forwarded-Proto) ainsi que le domaine spécifiée dans le champ Common Name du certificat utilisé le cas échéant. -Pour en savoir plus sur le ProxyProtocol, nous vous invitons à consulter la [spécification du ProxyProtocol](http://www.haproxy.org/download/1.8/doc/proxy-protocol.txt){.external}. +Pour en savoir plus sur le ProxyProtocol, nous vous invitons à consulter la [spécification du ProxyProtocol](http://www.haproxy.org/download/1.8/doc/proxy-protocol.txt). ## Activation du ProxyProtocol pour un de vos serveurs Le ProxyProtocol doit être activé pour chaque serveur enregistré dans une Ferme de serveurs. Cette fonctionnalité étant intrusive et ne pouvant être activée de manière transparente, cela permet de la tester sur une machine en particulier puis de déployer progressivement la configuration sur une ferme active. @@ -134,10 +134,10 @@ service nginx reload > Cet exemple utilise le protocole HTTP pour plus de simplicité. Si vous utilisez du HTTP, nous vous recommandons vivement d'utiliser les En-Têtes HTTP au lieu du ProxyProtocol sauf si votre service OVH Load Balancer est configuré en TCP. Cela peut se produire dans le cas d'une terminaison SSL pour du HTTP/2 par exemple. > -Pour plus d'informations sur la configuration du ProxyProtocol dans Nginx, nous vous invitons à consulter la documentation officielle du projet: [https://www.nginx.com/resources/admin-guide/proxy-protocol/](https://www.nginx.com/resources/admin-guide/proxy-protocol/){.external} +Pour plus d'informations sur la configuration du ProxyProtocol dans Nginx, nous vous invitons à consulter la documentation officielle du projet: [https://www.nginx.com/resources/admin-guide/proxy-protocol/](https://www.nginx.com/resources/admin-guide/proxy-protocol/) ### Apache -La gestion du ProxyProtocol dans Apache est encore jeune. Une implémentation non-officielle et compatible avec Apache 2.4 est disponible sur Github ([https://github.com/roadrunner2/mod-proxy-protocol](https://github.com/roadrunner2/mod-proxy-protocol){.external}) mais n'est plus maintenue depuis 2014. Une implémentation officielle se trouve dans le module mod_remoteip qui est également utilisé pour gérer les En-Têtes de la famille X-Forwarded-For. +La gestion du ProxyProtocol dans Apache est encore jeune. Une implémentation non-officielle et compatible avec Apache 2.4 est disponible sur Github ([https://github.com/roadrunner2/mod-proxy-protocol](https://github.com/roadrunner2/mod-proxy-protocol)) mais n'est plus maintenue depuis 2014. Une implémentation officielle se trouve dans le module mod_remoteip qui est également utilisé pour gérer les En-Têtes de la famille X-Forwarded-For. mod-proxy-protocol gère les version 1 et 2 du ProxyProtocol. En revanche, il ne permet pas de spécifier une liste d'IP source autorisées à utiliser le ProxyProtocol, bien que ce soit évoqué dans les projets du module. @@ -183,7 +183,7 @@ sudo apxs -i -a -c mod_proxy_protocol.c service apache2 restart ``` -Pour en savoir plus sur la configuration du module mod-proxy-protocol nous vous invitons à consulter sa documentation: [http://roadrunner2.github.io/mod-proxy-protocol/mod_proxy_protocol.html](http://roadrunner2.github.io/mod-proxy-protocol/mod_proxy_protocol.html){.external} +Pour en savoir plus sur la configuration du module mod-proxy-protocol nous vous invitons à consulter sa documentation: [http://roadrunner2.github.io/mod-proxy-protocol/mod_proxy_protocol.html](http://roadrunner2.github.io/mod-proxy-protocol/mod_proxy_protocol.html) #### Avec mod_remoteip - Le module étant expérimental, il faudra au préalable installé une version expérimentale de Apache, ce qui n'est pas recommandé dans une environnement de production, à moins de savoir précisément ce que l'on fait ! @@ -207,7 +207,7 @@ a2enmod remoteip service apache2 restart ``` -Pour en savoir plus sur la configuration du module mod_remoteip nous vous invitons à consulter sa documentation: [https://httpd.apache.org/docs/trunk/mod/mod_remoteip.html#remoteipproxyprotocol](https://httpd.apache.org/docs/trunk/mod/mod_remoteip.html#remoteipproxyprotocol){.external} +Pour en savoir plus sur la configuration du module mod_remoteip nous vous invitons à consulter sa documentation: [https://httpd.apache.org/docs/trunk/mod/mod_remoteip.html#remoteipproxyprotocol](https://httpd.apache.org/docs/trunk/mod/mod_remoteip.html#remoteipproxyprotocol) ### HAProxy Le ProxyProtocol a été conçu par l'équipe de HAProxy. Il est donc le logiciel gérant le mieux ce protocole. Cela pourra être utile dans un scénario où le suivi de la véritable IP source du client est indispensable mais le logiciel cible ne gère pas ce protocole. Ce sera le cas par exemple de MySQL et PostgreSQL pour n'en citer que 2. diff --git a/pages/network/load_balancer/create_proxyprotocol/guide.fr-fr.md b/pages/network/load_balancer/create_proxyprotocol/guide.fr-fr.md index ec6496e0936..cd052375827 100644 --- a/pages/network/load_balancer/create_proxyprotocol/guide.fr-fr.md +++ b/pages/network/load_balancer/create_proxyprotocol/guide.fr-fr.md @@ -58,7 +58,7 @@ La liste des IPv4 de sortie potentiellement utilisées par votre service OVHclou ### Présentation du ProxyProtocol -Le ProxyProtocol a été développé par l'équipe du Load Balancer [HAPRoxy](http://haproxy.org/){.external} comme l'homologue en TCP des en-têtes HTTP standards tels que X-Forwarded-For. Il a été pensé pour faire suivre au minimum : +Le ProxyProtocol a été développé par l'équipe du Load Balancer [HAPRoxy](http://haproxy.org/) comme l'homologue en TCP des en-têtes HTTP standards tels que X-Forwarded-For. Il a été pensé pour faire suivre au minimum : - le nom du protocole L4 utilisé (TCP4 pour l'IPv4 ou TCP6 pour l'IPv6); - l'adresse IPv4 ou IPv6 source; @@ -73,7 +73,7 @@ En effet, ce protocole existe en 2 versions : La version 1 étant largement suffisante pour la plupart des usages (bien que moins optimisée), elle est souvent la seule version gérée par les logiciels compatibles. La version 2 étant un format binaire, elle est plus rapide à analyser. Elle ajoute également la possibilité d'indiquer si la connexion d'origine était chiffrée (l'équivalent de l'en-tête X-Forwarded-Proto) ainsi que le domaine spécifié dans le champ Common Name du certificat utilisé le cas échéant. -Pour en savoir plus sur le ProxyProtocol, nous vous invitons à consulter la [spécification du ProxyProtocol](http://www.haproxy.org/download/1.8/doc/proxy-protocol.txt){.external}. +Pour en savoir plus sur le ProxyProtocol, nous vous invitons à consulter la [spécification du ProxyProtocol](http://www.haproxy.org/download/1.8/doc/proxy-protocol.txt). ### Activation du ProxyProtocol pour un de vos serveurs @@ -157,11 +157,11 @@ service nginx reload > Cet exemple utilise le protocole HTTP pour plus de simplicité. Si vous utilisez du HTTP, nous vous recommandons vivement d'utiliser les en-têtes HTTP au lieu du ProxyProtocol, sauf si votre service OVHcloud Load Balancer est configuré en TCP. Cela peut se produire dans le cas d'une terminaison SSL pour du HTTP/2 par exemple. > -Pour plus d'informations sur la configuration du ProxyProtocol dans Nginx, nous vous invitons à consulter [la documentation officielle du projet](https://www.nginx.com/resources/admin-guide/proxy-protocol/){.external}. +Pour plus d'informations sur la configuration du ProxyProtocol dans Nginx, nous vous invitons à consulter [la documentation officielle du projet](https://www.nginx.com/resources/admin-guide/proxy-protocol/). #### Apache -La gestion du ProxyProtocol dans Apache est encore jeune. Une implémentation non-officielle et compatible avec Apache 2.4 est disponible sur Github ([https://github.com/roadrunner2/mod-proxy-protocol](https://github.com/roadrunner2/mod-proxy-protocol){.external}) mais n'est plus maintenue depuis 2014. Une implémentation officielle se trouve dans le module `mod_remoteip` qui est également utilisé pour gérer les en-têtes de la famille X-Forwarded-For. +La gestion du ProxyProtocol dans Apache est encore jeune. Une implémentation non-officielle et compatible avec Apache 2.4 est disponible sur Github ([https://github.com/roadrunner2/mod-proxy-protocol](https://github.com/roadrunner2/mod-proxy-protocol)) mais n'est plus maintenue depuis 2014. Une implémentation officielle se trouve dans le module `mod_remoteip` qui est également utilisé pour gérer les en-têtes de la famille X-Forwarded-For. `mod-proxy-protocol` gère les versions 1 et 2 du ProxyProtocol. En revanche, il ne permet pas de spécifier une liste d'adresses IP source autorisées à utiliser le ProxyProtocol, bien que ce soit évoqué dans les projets du module. @@ -209,7 +209,7 @@ sudo apxs -i -a -c mod_proxy_protocol.c service apache2 restart ``` -Pour en savoir plus sur la configuration du module mod-proxy-protocol nous vous invitons à consulter [sa documentation](http://roadrunner2.github.io/mod-proxy-protocol/mod_proxy_protocol.html){.external}. +Pour en savoir plus sur la configuration du module mod-proxy-protocol nous vous invitons à consulter [sa documentation](http://roadrunner2.github.io/mod-proxy-protocol/mod_proxy_protocol.html). ##### **Avec mod_remoteip** @@ -234,7 +234,7 @@ a2enmod remoteip service apache2 restart ``` -Pour en savoir plus sur la configuration du module `mod_remoteip`, nous vous invitons à consulter [sa documentation](https://httpd.apache.org/docs/trunk/mod/mod_remoteip.html#remoteipproxyprotocol){.external}. +Pour en savoir plus sur la configuration du module `mod_remoteip`, nous vous invitons à consulter [sa documentation](https://httpd.apache.org/docs/trunk/mod/mod_remoteip.html#remoteipproxyprotocol). #### HAProxy diff --git a/pages/network/load_balancer/create_redirectlocation/guide.en-asia.md b/pages/network/load_balancer/create_redirectlocation/guide.en-asia.md index 0619b5b295b..c9f19f4e011 100644 --- a/pages/network/load_balancer/create_redirectlocation/guide.en-asia.md +++ b/pages/network/load_balancer/create_redirectlocation/guide.en-asia.md @@ -13,8 +13,8 @@ The OVH Load Balancer acts by default as a proxy. It can also be configured to r ## Requirements -- an [OVH Load Balancer](https://www.ovh.com/asia/solutions/load-balancer/){.external} -- access to the [OVH Control Panel](https://ca.ovh.com/auth/){.external}, or the [OVH API](/links/api){.external} +- an [OVH Load Balancer](https://www.ovh.com/asia/solutions/load-balancer/) +- access to the [OVH Control Panel](https://ca.ovh.com/auth/), or the [OVH API](/links/api) ## Instructions @@ -35,7 +35,7 @@ Custom redirections can be specified via the OVH Control Panel and via the API, ### Add a custom redirection via the OVH Control Panel. -You can define custom redirections from the [OVH Control Panel](https://ca.ovh.com/auth/){.external} by going to the `Cloud`{.action} section, then `Load Balancer`{.action}. +You can define custom redirections from the [OVH Control Panel](https://ca.ovh.com/auth/) by going to the `Cloud`{.action} section, then `Load Balancer`{.action}. You can either do this on a new front-end as you create it, or on an existing front-end. @@ -67,7 +67,7 @@ Once the front-end has been configured, click `Add`{.action} or `Edit`{.action}, ### Add a custom redirection via the API. -In the [OVH API](/links/api){.external}, redirections are specified in the redirectLocation character chain. +In the [OVH API](/links/api), redirections are specified in the redirectLocation character chain. * If you are creating a new front-end: diff --git a/pages/network/load_balancer/create_redirectlocation/guide.en-au.md b/pages/network/load_balancer/create_redirectlocation/guide.en-au.md index 7e1fe733fa4..36bdd99c755 100644 --- a/pages/network/load_balancer/create_redirectlocation/guide.en-au.md +++ b/pages/network/load_balancer/create_redirectlocation/guide.en-au.md @@ -13,8 +13,8 @@ The OVH Load Balancer acts by default as a proxy. It can also be configured to r ## Requirements -- an [OVH Load Balancer](https://www.ovh.com.au/solutions/load-balancer/){.external} -- access to the [OVH Control Panel](https://ca.ovh.com/auth/){.external}, or the [OVH API](/links/api){.external} +- an [OVH Load Balancer](https://www.ovh.com.au/solutions/load-balancer/) +- access to the [OVH Control Panel](https://ca.ovh.com/auth/), or the [OVH API](/links/api) ## Instructions @@ -35,7 +35,7 @@ Custom redirections can be specified via the OVH Control Panel and via the API, ### Add a custom redirection via the OVH Control Panel. -You can define custom redirections from the [OVH Control Panel](https://ca.ovh.com/auth/){.external} by going to the `Cloud`{.action} section, then `Load Balancer`{.action}. +You can define custom redirections from the [OVH Control Panel](https://ca.ovh.com/auth/) by going to the `Cloud`{.action} section, then `Load Balancer`{.action}. You can either do this on a new front-end as you create it, or on an existing front-end. @@ -67,7 +67,7 @@ Once the front-end has been configured, click `Add`{.action} or `Edit`{.action}, ### Add a custom redirection via the API. -In the [OVH API](/links/api){.external}, redirections are specified in the redirectLocation character chain. +In the [OVH API](/links/api), redirections are specified in the redirectLocation character chain. * If you are creating a new front-end: diff --git a/pages/network/load_balancer/create_redirectlocation/guide.en-ca.md b/pages/network/load_balancer/create_redirectlocation/guide.en-ca.md index 50f2d226b23..54e531c8aae 100644 --- a/pages/network/load_balancer/create_redirectlocation/guide.en-ca.md +++ b/pages/network/load_balancer/create_redirectlocation/guide.en-ca.md @@ -13,8 +13,8 @@ The OVH Load Balancer acts by default as a proxy. It can also be configured to r ## Requirements -- an [OVH Load Balancer](https://www.ovh.com/ca/en/solutions/load-balancer/){.external} -- access to the [OVH Control Panel](https://ca.ovh.com/auth/){.external}, or the [OVH API](/links/api){.external} +- an [OVH Load Balancer](https://www.ovh.com/ca/en/solutions/load-balancer/) +- access to the [OVH Control Panel](https://ca.ovh.com/auth/), or the [OVH API](/links/api) ## Instructions @@ -35,7 +35,7 @@ Custom redirections can be specified via the OVH Control Panel and via the API, ### Add a custom redirection via the OVH Control Panel. -You can define custom redirections from the [OVH Control Panel](https://ca.ovh.com/auth/){.external} by going to the `Cloud`{.action} section, then `Load Balancer`{.action}. +You can define custom redirections from the [OVH Control Panel](https://ca.ovh.com/auth/) by going to the `Cloud`{.action} section, then `Load Balancer`{.action}. You can either do this on a new front-end as you create it, or on an existing front-end. @@ -67,7 +67,7 @@ Once the front-end has been configured, click `Add`{.action} or `Edit`{.action}, ### Add a custom redirection via the API. -In the [OVH API](/links/api){.external}, redirections are specified in the redirectLocation character chain. +In the [OVH API](/links/api), redirections are specified in the redirectLocation character chain. * If you are creating a new front-end: diff --git a/pages/network/load_balancer/create_redirectlocation/guide.en-gb.md b/pages/network/load_balancer/create_redirectlocation/guide.en-gb.md index 68328a47487..beb4d27a80e 100644 --- a/pages/network/load_balancer/create_redirectlocation/guide.en-gb.md +++ b/pages/network/load_balancer/create_redirectlocation/guide.en-gb.md @@ -13,8 +13,8 @@ The OVH Load Balancer acts by default as a proxy. It can also be configured to r ## Requirements -- an [OVH Load Balancer](/links/network/load-balancer){.external} -- access to the [OVH Control Panel](/links/manager){.external}, or the [OVH API](/links/api){.external} +- an [OVH Load Balancer](/links/network/load-balancer) +- access to the [OVH Control Panel](/links/manager), or the [OVH API](/links/api) ## Instructions @@ -35,7 +35,7 @@ Custom redirections can be specified via the OVH Control Panel and via the API, ### Add a custom redirection via the OVH Control Panel. -You can define custom redirections from the [OVH Control Panel](/links/manager){.external} by going to the `Cloud`{.action} section, then `Load Balancer`{.action}. +You can define custom redirections from the [OVH Control Panel](/links/manager) by going to the `Cloud`{.action} section, then `Load Balancer`{.action}. You can either do this on a new front-end as you create it, or on an existing front-end. @@ -67,7 +67,7 @@ Once the front-end has been configured, click `Add`{.action} or `Edit`{.action}, ### Add a custom redirection via the API. -In the [OVH API](/links/api){.external}, redirections are specified in the redirectLocation character chain. +In the [OVH API](/links/api), redirections are specified in the redirectLocation character chain. * If you are creating a new front-end: diff --git a/pages/network/load_balancer/create_redirectlocation/guide.en-sg.md b/pages/network/load_balancer/create_redirectlocation/guide.en-sg.md index ea3142ee4da..07daa87e4e1 100644 --- a/pages/network/load_balancer/create_redirectlocation/guide.en-sg.md +++ b/pages/network/load_balancer/create_redirectlocation/guide.en-sg.md @@ -13,8 +13,8 @@ The OVH Load Balancer acts by default as a proxy. It can also be configured to r ## Requirements -- an [OVH Load Balancer](https://www.ovh.com/sg/solutions/load-balancer/){.external} -- access to the [OVH Control Panel](https://ca.ovh.com/auth/){.external}, or the [OVH API](/links/api){.external} +- an [OVH Load Balancer](https://www.ovh.com/sg/solutions/load-balancer/) +- access to the [OVH Control Panel](https://ca.ovh.com/auth/), or the [OVH API](/links/api) ## Instructions @@ -35,7 +35,7 @@ Custom redirections can be specified via the OVH Control Panel and via the API, ### Add a custom redirection via the OVH Control Panel. -You can define custom redirections from the [OVH Control Panel](https://ca.ovh.com/auth/){.external} by going to the `Cloud`{.action} section, then `Load Balancer`{.action}. +You can define custom redirections from the [OVH Control Panel](https://ca.ovh.com/auth/) by going to the `Cloud`{.action} section, then `Load Balancer`{.action}. You can either do this on a new front-end as you create it, or on an existing front-end. @@ -67,7 +67,7 @@ Once the front-end has been configured, click `Add`{.action} or `Edit`{.action}, ### Add a custom redirection via the API. -In the [OVH API](/links/api){.external}, redirections are specified in the redirectLocation character chain. +In the [OVH API](/links/api), redirections are specified in the redirectLocation character chain. * If you are creating a new front-end: diff --git a/pages/network/load_balancer/create_redirectlocation/guide.en-us.md b/pages/network/load_balancer/create_redirectlocation/guide.en-us.md index 698cd68f0aa..be330d7c78a 100644 --- a/pages/network/load_balancer/create_redirectlocation/guide.en-us.md +++ b/pages/network/load_balancer/create_redirectlocation/guide.en-us.md @@ -13,8 +13,8 @@ The OVH Load Balancer acts by default as a proxy. It can also be configured to r ## Requirements -- an [OVH Load Balancer](https://www.ovh.com/world/solutions/load-balancer/){.external} -- access to the [OVH Control Panel](https://ca.ovh.com/auth/){.external}, or the [OVH API](/links/api){.external} +- an [OVH Load Balancer](https://www.ovh.com/world/solutions/load-balancer/) +- access to the [OVH Control Panel](https://ca.ovh.com/auth/), or the [OVH API](/links/api) ## Instructions @@ -35,7 +35,7 @@ Custom redirections can be specified via the OVH Control Panel and via the API, ### Add a custom redirection via the OVH Control Panel. -You can define custom redirections from the [OVH Control Panel](https://ca.ovh.com/auth/){.external} by going to the `Cloud`{.action} section, then `Load Balancer`{.action}. +You can define custom redirections from the [OVH Control Panel](https://ca.ovh.com/auth/) by going to the `Cloud`{.action} section, then `Load Balancer`{.action}. You can either do this on a new front-end as you create it, or on an existing front-end. @@ -67,7 +67,7 @@ Once the front-end has been configured, click `Add`{.action} or `Edit`{.action}, ### Add a custom redirection via the API. -In the [OVH API](/links/api){.external}, redirections are specified in the redirectLocation character chain. +In the [OVH API](/links/api), redirections are specified in the redirectLocation character chain. * If you are creating a new front-end: diff --git a/pages/network/load_balancer/create_redirectlocation/guide.fr-ca.md b/pages/network/load_balancer/create_redirectlocation/guide.fr-ca.md index 79c1855dc6e..580e9f6f812 100644 --- a/pages/network/load_balancer/create_redirectlocation/guide.fr-ca.md +++ b/pages/network/load_balancer/create_redirectlocation/guide.fr-ca.md @@ -11,10 +11,10 @@ Le service OVH Load Balancer agit par défault comme un mandataire ou "Proxy". I ## Prérequis -- Disposer d'un [Load Balancer OVH](https://www.ovh.com/ca/fr/solutions/load-balancer/){.external}. +- Disposer d'un [Load Balancer OVH](https://www.ovh.com/ca/fr/solutions/load-balancer/). - Avoir accès : - - à l'[espace client OVH](/links/manager){.external}, ou bien - - à l'[API OVH](/links/api){.external}. + - à l'[espace client OVH](/links/manager), ou bien + - à l'[API OVH](/links/api). ## En pratique @@ -35,7 +35,7 @@ Les Redirections personnalisées peuvent être spécifiées via le Manager et vi ### Ajouter une redirection personnalisée via le Manager -Il est possible de définir une redirection personnalisée depuis l'[espace client](/links/manager){.external} dans la partie `Cloud`{.action}, section `Load Balancer`{.action}. +Il est possible de définir une redirection personnalisée depuis l'[espace client](/links/manager) dans la partie `Cloud`{.action}, section `Load Balancer`{.action}. Cela peut-être effectué tant sur un nouveau Frontend pendant sa création, que sur un Frontend existant. * Ajout d'un nouveau Frontend @@ -76,7 +76,7 @@ cliquez sur `Appliquer la configuration`{.action}. ### Ajouter une redirection personnalisée via l'API -Dans l'[API OVH](/links/api){.external}, les Redirections sont spécifiées dans la chaîne de caractère redirectLocation : +Dans l'[API OVH](/links/api), les Redirections sont spécifiées dans la chaîne de caractère redirectLocation : * création d'un nouveau Frontend diff --git a/pages/network/load_balancer/create_redirectlocation/guide.fr-fr.md b/pages/network/load_balancer/create_redirectlocation/guide.fr-fr.md index 2c4c9bb6e92..dbaa2bf8b4f 100644 --- a/pages/network/load_balancer/create_redirectlocation/guide.fr-fr.md +++ b/pages/network/load_balancer/create_redirectlocation/guide.fr-fr.md @@ -12,7 +12,7 @@ Le service OVHcloud Load Balancer agit par défaut comme un mandataire ou « Pro - Posséder une offre [OVHcloud Load balancer](/links/network/load-balancer) dans votre compte OVHcloud. - Être connecté à votre [espace client OVHcloud](/links/manager). -- Être connecté à l'[API OVHcloud](/links/api){.external}. +- Être connecté à l'[API OVHcloud](/links/api). ## En pratique @@ -33,7 +33,7 @@ Les redirections personnalisées peuvent être spécifiées via l'espace client ### Ajouter une redirection personnalisée depuis l'espace client OVHcloud -Il est possible de définir une redirection personnalisée depuis l'[espace client OVHcloud](/links/manager){.external} dans la partie `Bare Metal Cloud`{.action} puis `Load Balancer`{.action}. +Il est possible de définir une redirection personnalisée depuis l'[espace client OVHcloud](/links/manager) dans la partie `Bare Metal Cloud`{.action} puis `Load Balancer`{.action}. Cela peut-être effectué tant sur un nouveau frontend pendant sa création, que sur un frontend existant. #### Ajout d'un nouveau frontend @@ -67,7 +67,7 @@ Pour ce faire, vous pouvez au choix : ### Ajouter une redirection personnalisée depuis l'API OVHcloud -Dans l'[API OVHcloud](/links/api){.external}, les redirections sont spécifiées dans la chaîne de caractère redirectLocation : +Dans l'[API OVHcloud](/links/api), les redirections sont spécifiées dans la chaîne de caractère redirectLocation : #### Création d'un nouveau frontend diff --git a/pages/network/load_balancer/create_route/guide.en-asia.md b/pages/network/load_balancer/create_route/guide.en-asia.md index e62467bb83e..cb18ec7ebc2 100644 --- a/pages/network/load_balancer/create_route/guide.en-asia.md +++ b/pages/network/load_balancer/create_route/guide.en-asia.md @@ -14,8 +14,8 @@ In some cases, you can go a step further and route, redirect or block traffic ac ## Requirements -- an [OVH Load Balancer](https://www.ovh.com/asia/solutions/load-balancer/){.external} on a solution that lets you create routes -- access to the [OVH API](/links/api){.external} +- an [OVH Load Balancer](https://www.ovh.com/asia/solutions/load-balancer/) on a solution that lets you create routes +- access to the [OVH API](/links/api) ## Instructions @@ -43,7 +43,7 @@ This is what is known as an ‘end action’. It means that if the rules are con ## An introduction to the API. -You can only manage routes via the [OVH API](/links/api){.external}. It is only valid for `http`{.action} and `tcp`{.action} protocols, and the `/ipLoadbalancing/{serviceName}/{protocol}/route/`{.action} pathway exposes the API dedicated to routes. +You can only manage routes via the [OVH API](/links/api). It is only valid for `http`{.action} and `tcp`{.action} protocols, and the `/ipLoadbalancing/{serviceName}/{protocol}/route/`{.action} pathway exposes the API dedicated to routes. The API for routes to the OVH Load Balancer is specially designed for flexibility, power and scalability. It is organised around three main sections: @@ -118,7 +118,7 @@ You can read about API calls in more detail in the [Edit routes](#edit-routes){. HTTPS protocol has become the norm. Its purpose is to make all websites available securely in HTTPS, with the SSL/TLS protocol. If you need an SSL/TLS certificate, you can use the OVH Load Balancer service to order a new one, which will be automatically managed for you. -Migrating a website to HTTPS involves a lot of work, especially to avoid [mixed content](https://developer.mozilla.org/en-us/docs/Web/Security/Mixed_content){.external}. It may be worth migrating your website section by section, and starting by securing pages that send login credentials. +Migrating a website to HTTPS involves a lot of work, especially to avoid [mixed content](https://developer.mozilla.org/en-us/docs/Web/Security/Mixed_content). It may be worth migrating your website section by section, and starting by securing pages that send login credentials. One approach could be to base it on the beginning of WordPress URLs. By default, the URL the login pages for WordPress start with "/wp-login". So we would need: diff --git a/pages/network/load_balancer/create_route/guide.en-au.md b/pages/network/load_balancer/create_route/guide.en-au.md index dc8c9d837e4..3cbe31f9b34 100644 --- a/pages/network/load_balancer/create_route/guide.en-au.md +++ b/pages/network/load_balancer/create_route/guide.en-au.md @@ -14,8 +14,8 @@ In some cases, you can go a step further and route, redirect or block traffic ac ## Requirements -- an [OVH Load Balancer](https://www.ovh.com.au/solutions/load-balancer/){.external} on a solution that lets you create routes -- access to the [OVH API](/links/api){.external} +- an [OVH Load Balancer](https://www.ovh.com.au/solutions/load-balancer/) on a solution that lets you create routes +- access to the [OVH API](/links/api) ## Instructions @@ -43,7 +43,7 @@ This is what is known as an ‘end action’. It means that if the rules are con ## An introduction to the API. -You can only manage routes via the [OVH API](/links/api){.external}. It is only valid for `http`{.action} and `tcp`{.action} protocols, and the `/ipLoadbalancing/{serviceName}/{protocol}/route/`{.action} pathway exposes the API dedicated to routes. +You can only manage routes via the [OVH API](/links/api). It is only valid for `http`{.action} and `tcp`{.action} protocols, and the `/ipLoadbalancing/{serviceName}/{protocol}/route/`{.action} pathway exposes the API dedicated to routes. The API for routes to the OVH Load Balancer is specially designed for flexibility, power and scalability. It is organised around three main sections: @@ -118,7 +118,7 @@ You can read about API calls in more detail in the [Edit routes](#edit-routes){. HTTPS protocol has become the norm. Its purpose is to make all websites available securely in HTTPS, with the SSL/TLS protocol. If you need an SSL/TLS certificate, you can use the OVH Load Balancer service to order a new one, which will be automatically managed for you. -Migrating a website to HTTPS involves a lot of work, especially to avoid [mixed content](https://developer.mozilla.org/en-us/docs/Web/Security/Mixed_content){.external}. It may be worth migrating your website section by section, and starting by securing pages that send login credentials. +Migrating a website to HTTPS involves a lot of work, especially to avoid [mixed content](https://developer.mozilla.org/en-us/docs/Web/Security/Mixed_content). It may be worth migrating your website section by section, and starting by securing pages that send login credentials. One approach could be to base it on the beginning of WordPress URLs. By default, the URL the login pages for WordPress start with "/wp-login". So we would need: diff --git a/pages/network/load_balancer/create_route/guide.en-ca.md b/pages/network/load_balancer/create_route/guide.en-ca.md index 017713dd805..b7830c408dd 100644 --- a/pages/network/load_balancer/create_route/guide.en-ca.md +++ b/pages/network/load_balancer/create_route/guide.en-ca.md @@ -14,8 +14,8 @@ In some cases, you can go a step further and route, redirect or block traffic ac ## Requirements -- an [OVH Load Balancer](https://www.ovh.com/ca/en/solutions/load-balancer/){.external} on a solution that lets you create routes -- access to the [OVH API](/links/api){.external} +- an [OVH Load Balancer](https://www.ovh.com/ca/en/solutions/load-balancer/) on a solution that lets you create routes +- access to the [OVH API](/links/api) ## Instructions @@ -43,7 +43,7 @@ This is what is known as an ‘end action’. It means that if the rules are con ## An introduction to the API. -You can only manage routes via the [OVH API](/links/api){.external}. It is only valid for `http`{.action} and `tcp`{.action} protocols, and the `/ipLoadbalancing/{serviceName}/{protocol}/route/`{.action} pathway exposes the API dedicated to routes. +You can only manage routes via the [OVH API](/links/api). It is only valid for `http`{.action} and `tcp`{.action} protocols, and the `/ipLoadbalancing/{serviceName}/{protocol}/route/`{.action} pathway exposes the API dedicated to routes. The API for routes to the OVH Load Balancer is specially designed for flexibility, power and scalability. It is organised around three main sections: @@ -118,7 +118,7 @@ You can read about API calls in more detail in the [Edit routes](#edit-routes){. HTTPS protocol has become the norm. Its purpose is to make all websites available securely in HTTPS, with the SSL/TLS protocol. If you need an SSL/TLS certificate, you can use the OVH Load Balancer service to order a new one, which will be automatically managed for you. -Migrating a website to HTTPS involves a lot of work, especially to avoid [mixed content](https://developer.mozilla.org/en-us/docs/Web/Security/Mixed_content){.external}. It may be worth migrating your website section by section, and starting by securing pages that send login credentials. +Migrating a website to HTTPS involves a lot of work, especially to avoid [mixed content](https://developer.mozilla.org/en-us/docs/Web/Security/Mixed_content). It may be worth migrating your website section by section, and starting by securing pages that send login credentials. One approach could be to base it on the beginning of WordPress URLs. By default, the URL the login pages for WordPress start with "/wp-login". So we would need: diff --git a/pages/network/load_balancer/create_route/guide.en-gb.md b/pages/network/load_balancer/create_route/guide.en-gb.md index bff51e6384d..b904f97ce75 100644 --- a/pages/network/load_balancer/create_route/guide.en-gb.md +++ b/pages/network/load_balancer/create_route/guide.en-gb.md @@ -14,8 +14,8 @@ In some cases, you can go a step further and route, redirect or block traffic ac ## Requirements -- an [OVH Load Balancer](/links/network/load-balancer){.external} on a solution that lets you create routes -- access to the [OVH API](/links/api){.external} +- an [OVH Load Balancer](/links/network/load-balancer) on a solution that lets you create routes +- access to the [OVH API](/links/api) ## Instructions @@ -43,7 +43,7 @@ This is what is known as an ‘end action’. It means that if the rules are con ## An introduction to the API. -You can only manage routes via the [OVH API](/links/api){.external}. It is only valid for `http`{.action} and `tcp`{.action} protocols, and the `/ipLoadbalancing/{serviceName}/{protocol}/route/`{.action} pathway exposes the API dedicated to routes. +You can only manage routes via the [OVH API](/links/api). It is only valid for `http`{.action} and `tcp`{.action} protocols, and the `/ipLoadbalancing/{serviceName}/{protocol}/route/`{.action} pathway exposes the API dedicated to routes. The API for routes to the OVH Load Balancer is specially designed for flexibility, power and scalability. It is organised around three main sections: @@ -118,7 +118,7 @@ You can read about API calls in more detail in the [Edit routes](#edit-routes){. HTTPS protocol has become the norm. Its purpose is to make all websites available securely in HTTPS, with the SSL/TLS protocol. If you need an SSL/TLS certificate, you can use the OVH Load Balancer service to order a new one, which will be automatically managed for you. -Migrating a website to HTTPS involves a lot of work, especially to avoid [mixed content](https://developer.mozilla.org/en-us/docs/Web/Security/Mixed_content){.external}. It may be worth migrating your website section by section, and starting by securing pages that send login credentials. +Migrating a website to HTTPS involves a lot of work, especially to avoid [mixed content](https://developer.mozilla.org/en-us/docs/Web/Security/Mixed_content). It may be worth migrating your website section by section, and starting by securing pages that send login credentials. One approach could be to base it on the beginning of WordPress URLs. By default, the URL the login pages for WordPress start with "/wp-login". So we would need: diff --git a/pages/network/load_balancer/create_route/guide.en-sg.md b/pages/network/load_balancer/create_route/guide.en-sg.md index dd183ddafa7..9e166eec1fe 100644 --- a/pages/network/load_balancer/create_route/guide.en-sg.md +++ b/pages/network/load_balancer/create_route/guide.en-sg.md @@ -14,8 +14,8 @@ In some cases, you can go a step further and route, redirect or block traffic ac ## Requirements -- an [OVH Load Balancer](https://www.ovh.com/sg/solutions/load-balancer/){.external} on a solution that lets you create routes -- access to the [OVH API](/links/api){.external} +- an [OVH Load Balancer](https://www.ovh.com/sg/solutions/load-balancer/) on a solution that lets you create routes +- access to the [OVH API](/links/api) ## Instructions @@ -43,7 +43,7 @@ This is what is known as an ‘end action’. It means that if the rules are con ## An introduction to the API. -You can only manage routes via the [OVH API](/links/api){.external}. It is only valid for `http`{.action} and `tcp`{.action} protocols, and the `/ipLoadbalancing/{serviceName}/{protocol}/route/`{.action} pathway exposes the API dedicated to routes. +You can only manage routes via the [OVH API](/links/api). It is only valid for `http`{.action} and `tcp`{.action} protocols, and the `/ipLoadbalancing/{serviceName}/{protocol}/route/`{.action} pathway exposes the API dedicated to routes. The API for routes to the OVH Load Balancer is specially designed for flexibility, power and scalability. It is organised around three main sections: @@ -118,7 +118,7 @@ You can read about API calls in more detail in the [Edit routes](#edit-routes){. HTTPS protocol has become the norm. Its purpose is to make all websites available securely in HTTPS, with the SSL/TLS protocol. If you need an SSL/TLS certificate, you can use the OVH Load Balancer service to order a new one, which will be automatically managed for you. -Migrating a website to HTTPS involves a lot of work, especially to avoid [mixed content](https://developer.mozilla.org/en-us/docs/Web/Security/Mixed_content){.external}. It may be worth migrating your website section by section, and starting by securing pages that send login credentials. +Migrating a website to HTTPS involves a lot of work, especially to avoid [mixed content](https://developer.mozilla.org/en-us/docs/Web/Security/Mixed_content). It may be worth migrating your website section by section, and starting by securing pages that send login credentials. One approach could be to base it on the beginning of WordPress URLs. By default, the URL the login pages for WordPress start with "/wp-login". So we would need: diff --git a/pages/network/load_balancer/create_route/guide.en-us.md b/pages/network/load_balancer/create_route/guide.en-us.md index c0c2d76704d..206a3ae26d9 100644 --- a/pages/network/load_balancer/create_route/guide.en-us.md +++ b/pages/network/load_balancer/create_route/guide.en-us.md @@ -14,8 +14,8 @@ In some cases, you can go a step further and route, redirect or block traffic ac ## Requirements -- an [OVH Load Balancer](https://www.ovh.com/world/solutions/load-balancer/){.external} on a solution that lets you create routes -- access to the [OVH API](/links/api){.external} +- an [OVH Load Balancer](https://www.ovh.com/world/solutions/load-balancer/) on a solution that lets you create routes +- access to the [OVH API](/links/api) ## Instructions @@ -43,7 +43,7 @@ This is what is known as an ‘end action’. It means that if the rules are con ## An introduction to the API. -You can only manage routes via the [OVH API](/links/api){.external}. It is only valid for `http`{.action} and `tcp`{.action} protocols, and the `/ipLoadbalancing/{serviceName}/{protocol}/route/`{.action} pathway exposes the API dedicated to routes. +You can only manage routes via the [OVH API](/links/api). It is only valid for `http`{.action} and `tcp`{.action} protocols, and the `/ipLoadbalancing/{serviceName}/{protocol}/route/`{.action} pathway exposes the API dedicated to routes. The API for routes to the OVH Load Balancer is specially designed for flexibility, power and scalability. It is organised around three main sections: @@ -118,7 +118,7 @@ You can read about API calls in more detail in the [Edit routes](#edit-routes){. HTTPS protocol has become the norm. Its purpose is to make all websites available securely in HTTPS, with the SSL/TLS protocol. If you need an SSL/TLS certificate, you can use the OVH Load Balancer service to order a new one, which will be automatically managed for you. -Migrating a website to HTTPS involves a lot of work, especially to avoid [mixed content](https://developer.mozilla.org/en-us/docs/Web/Security/Mixed_content){.external}. It may be worth migrating your website section by section, and starting by securing pages that send login credentials. +Migrating a website to HTTPS involves a lot of work, especially to avoid [mixed content](https://developer.mozilla.org/en-us/docs/Web/Security/Mixed_content). It may be worth migrating your website section by section, and starting by securing pages that send login credentials. One approach could be to base it on the beginning of WordPress URLs. By default, the URL the login pages for WordPress start with "/wp-login". So we would need: diff --git a/pages/network/load_balancer/create_route/guide.fr-ca.md b/pages/network/load_balancer/create_route/guide.fr-ca.md index e47266dd4ea..953817cf22c 100644 --- a/pages/network/load_balancer/create_route/guide.fr-ca.md +++ b/pages/network/load_balancer/create_route/guide.fr-ca.md @@ -12,8 +12,8 @@ Dans certains cas, il est possible d'aller plus loin, et de router, rediriger ou ## Prérequis -- Disposer d'un [Load Balancer OVH](https://www.ovh.com/ca/fr/solutions/load-balancer/){.external} sur une offre autorisant la création des routes -- Avoir accès à l'[API OVH](/links/api){.external}. +- Disposer d'un [Load Balancer OVH](https://www.ovh.com/ca/fr/solutions/load-balancer/) sur une offre autorisant la création des routes +- Avoir accès à l'[API OVH](/links/api). ## En pratique @@ -41,7 +41,7 @@ Il s'agit d'une action « finale ». C'est à dire que si les règles sont valid ## Présentation de l'API -La gestion des routes n'est accessible qu'au travers de l'[API OVH](/links/api){.external}. Elle est valide uniquement pour les protocoles `http`{.action} et `tcp`{.action}, le chemin `/ipLoadbalancing/{serviceName}/{protocole}/route/`{.action} expose l'API dédiée aux routes. +La gestion des routes n'est accessible qu'au travers de l'[API OVH](/links/api). Elle est valide uniquement pour les protocoles `http`{.action} et `tcp`{.action}, le chemin `/ipLoadbalancing/{serviceName}/{protocole}/route/`{.action} expose l'API dédiée aux routes. L'API des routes de votre service OVH Load Balancer a été pensée spécialement pour être souple, puissante et évolutive. Elle est organisée autour de trois sections principales : @@ -111,7 +111,7 @@ Vous trouverez le détail des appels d'API dans la section [Manipulation des rou ### Forcer le HTTPS pour les pages de login WordPress Le HTTPS est devenu la norme. L'objectif est de rendre tous les sites disponibles de manière sécurisée en HTTPS grâce au protocole SSL/TLS. Si vous avez besoin d'un certificat SSL/TLS, vous pouvez utiliser votre service OVH Load Balancer pour en commander un qui sera géré pour vous de manière complètement automatique. -Migrer un site en HTTPS demande du travail, notamment pour éviter les problèmes de "[Mixed-Content](https://developer.mozilla.org/en-us/docs/Web/Security/Mixed_content){.external}". Il peut être intéressant de migrer section par section, en commençant par sécuriser les pages envoyant des identifiants. +Migrer un site en HTTPS demande du travail, notamment pour éviter les problèmes de "[Mixed-Content](https://developer.mozilla.org/en-us/docs/Web/Security/Mixed_content)". Il peut être intéressant de migrer section par section, en commençant par sécuriser les pages envoyant des identifiants. Une approche pourrait être de se baser sur le début des URLs WordPress. Par défaut, l'URL des pages de connexion de WordPress commencent par "/wp-login". Nous aurions donc besoin : diff --git a/pages/network/load_balancer/create_route/guide.fr-fr.md b/pages/network/load_balancer/create_route/guide.fr-fr.md index d01f0d692c4..813922162de 100644 --- a/pages/network/load_balancer/create_route/guide.fr-fr.md +++ b/pages/network/load_balancer/create_route/guide.fr-fr.md @@ -12,8 +12,8 @@ Dans certains cas, il est possible d'aller plus loin et de router, rediriger ou ## Prérequis -- Disposer d'un [Load Balancer OVHcloud](/links/network/load-balancer){.external} sur une offre autorisant la création des routes. -- Avoir accès à l'[API OVHcloud](/links/api){.external}. +- Disposer d'un [Load Balancer OVHcloud](/links/network/load-balancer) sur une offre autorisant la création des routes. +- Avoir accès à l'[API OVHcloud](/links/api). ## En pratique @@ -41,7 +41,7 @@ Il s'agit d'une action « finale ». C'est à dire que si les règles sont valid ### Présentation de l'API -La gestion des routes n'est accessible qu'au travers de l'[API OVHcloud](/links/api){.external}. Elle est valide uniquement pour les protocoles `http` et `tcp`{.action}, le chemin `/ipLoadbalancing/{serviceName}/{protocole}/route/` expose l'API dédiée aux routes. +La gestion des routes n'est accessible qu'au travers de l'[API OVHcloud](/links/api). Elle est valide uniquement pour les protocoles `http` et `tcp`{.action}, le chemin `/ipLoadbalancing/{serviceName}/{protocole}/route/` expose l'API dédiée aux routes. L'API des routes de votre service OVHcloud Load Balancer a été pensée spécialement pour être souple, puissante et évolutive. Elle est organisée autour de trois sections principales : @@ -117,7 +117,7 @@ Vous trouverez le détail des appels d'API dans la section « [Manipulation des Le HTTPS est devenu la norme. L'objectif est de rendre tous les sites disponibles de manière sécurisée en HTTPS grâce au protocole SSL/TLS. Si vous avez besoin d'un certificat SSL/TLS, vous pouvez utiliser votre service OVHcloud Load Balancer pour en commander un qui sera géré pour vous de manière complètement automatique. -Migrer un site en HTTPS demande du travail, notamment pour éviter les problèmes de « [Mixed-Content](https://developer.mozilla.org/en-us/docs/Web/Security/Mixed_content){.external} ». Il peut être intéressant de migrer section par section, en commençant par sécuriser les pages envoyant des identifiants. +Migrer un site en HTTPS demande du travail, notamment pour éviter les problèmes de « [Mixed-Content](https://developer.mozilla.org/en-us/docs/Web/Security/Mixed_content) ». Il peut être intéressant de migrer section par section, en commençant par sécuriser les pages envoyant des identifiants. Une approche pourrait être de se baser sur le début des URLs WordPress. Par défaut, l'URL des pages de connexion de WordPress commencent par `/wp-login`. Nous aurions donc besoin : diff --git a/pages/network/load_balancer/create_stickiness/guide.en-asia.md b/pages/network/load_balancer/create_stickiness/guide.en-asia.md index 832a943cf2d..50e22e881ac 100644 --- a/pages/network/load_balancer/create_stickiness/guide.en-asia.md +++ b/pages/network/load_balancer/create_stickiness/guide.en-asia.md @@ -6,7 +6,7 @@ updated: 2021-02-05 ## Objective -The [OVH Load Balancer](https://www.ovh.com/asia/solutions/load-balancer/){.external} service offers a number of ways of tracking connections to your services. +The [OVH Load Balancer](https://www.ovh.com/asia/solutions/load-balancer/) service offers a number of ways of tracking connections to your services. Each session on the OVH Load Balancer service is maintained by a persistent connection system. The system is configured on the application layer of the OVH Load Balancer service, and it maintains a persistent connection to the server. @@ -16,8 +16,8 @@ This guide provides an introduction to the ways in which you can configure these ## Requirements -- an [OVH Load Balancer](https://www.ovh.com/asia/solutions/load-balancer/){.external} -- access to the [OVH Control Panel](/links/manager){.external}, or the [OVH API](/links/api){.external} +- an [OVH Load Balancer](https://www.ovh.com/asia/solutions/load-balancer/) +- access to the [OVH Control Panel](/links/manager), or the [OVH API](/links/api) ## Instructions diff --git a/pages/network/load_balancer/create_stickiness/guide.en-au.md b/pages/network/load_balancer/create_stickiness/guide.en-au.md index f4d6279d1aa..52c5ef70501 100644 --- a/pages/network/load_balancer/create_stickiness/guide.en-au.md +++ b/pages/network/load_balancer/create_stickiness/guide.en-au.md @@ -6,7 +6,7 @@ updated: 2021-02-05 ## Objective -The [OVH Load Balancer](https://www.ovh.com/world/solutions/load-balancer/){.external} service offers a number of ways of tracking connections to your services. +The [OVH Load Balancer](https://www.ovh.com/world/solutions/load-balancer/) service offers a number of ways of tracking connections to your services. Each session on the OVH Load Balancer service is maintained by a persistent connection system. The system is configured on the application layer of the OVH Load Balancer service, and it maintains a persistent connection to the server. @@ -16,8 +16,8 @@ This guide provides an introduction to the ways in which you can configure these ## Requirements -- an [OVH Load Balancer](https://www.ovh.com.au/solutions/load-balancer/){.external} -- access to the [OVH Control Panel](/links/manager){.external}, or the [OVH API](/links/api){.external} +- an [OVH Load Balancer](https://www.ovh.com.au/solutions/load-balancer/) +- access to the [OVH Control Panel](/links/manager), or the [OVH API](/links/api) ## Instructions diff --git a/pages/network/load_balancer/create_stickiness/guide.en-ca.md b/pages/network/load_balancer/create_stickiness/guide.en-ca.md index 397250d2869..8c0fcf2cb20 100644 --- a/pages/network/load_balancer/create_stickiness/guide.en-ca.md +++ b/pages/network/load_balancer/create_stickiness/guide.en-ca.md @@ -6,7 +6,7 @@ updated: 2021-02-05 ## Objective -The [OVH Load Balancer](https://www.ovh.com/ca/en/solutions/load-balancer/){.external} service offers a number of ways of tracking connections to your services. +The [OVH Load Balancer](https://www.ovh.com/ca/en/solutions/load-balancer/) service offers a number of ways of tracking connections to your services. Each session on the OVH Load Balancer service is maintained by a persistent connection system. The system is configured on the application layer of the OVH Load Balancer service, and it maintains a persistent connection to the server. @@ -16,8 +16,8 @@ This guide provides an introduction to the ways in which you can configure these ## Requirements -- an [OVH Load Balancer](https://www.ovh.com/ca/en/solutions/load-balancer/){.external} -- access to the [OVH Control Panel](/links/manager){.external}, or the [OVH API](/links/api){.external} +- an [OVH Load Balancer](https://www.ovh.com/ca/en/solutions/load-balancer/) +- access to the [OVH Control Panel](/links/manager), or the [OVH API](/links/api) ## Instructions diff --git a/pages/network/load_balancer/create_stickiness/guide.en-gb.md b/pages/network/load_balancer/create_stickiness/guide.en-gb.md index 889dc898023..3bff5c9dc92 100644 --- a/pages/network/load_balancer/create_stickiness/guide.en-gb.md +++ b/pages/network/load_balancer/create_stickiness/guide.en-gb.md @@ -6,7 +6,7 @@ updated: 2021-02-05 ## Objective -The [OVH Load Balancer](/links/network/load-balancer){.external} service offers a number of ways of tracking connections to your services. +The [OVH Load Balancer](/links/network/load-balancer) service offers a number of ways of tracking connections to your services. Each session on the OVH Load Balancer service is maintained by a persistent connection system. The system is configured on the application layer of the OVH Load Balancer service, and it maintains a persistent connection to the server. @@ -16,8 +16,8 @@ This guide provides an introduction to the ways in which you can configure these ## Requirements -- an [OVH Load Balancer](/links/network/load-balancer){.external} -- access to the [OVH Control Panel](/links/manager){.external}, or the [OVH API](/links/api){.external} +- an [OVH Load Balancer](/links/network/load-balancer) +- access to the [OVH Control Panel](/links/manager), or the [OVH API](/links/api) ## Instructions diff --git a/pages/network/load_balancer/create_stickiness/guide.en-sg.md b/pages/network/load_balancer/create_stickiness/guide.en-sg.md index b46ea44e155..f644520a1c2 100644 --- a/pages/network/load_balancer/create_stickiness/guide.en-sg.md +++ b/pages/network/load_balancer/create_stickiness/guide.en-sg.md @@ -6,7 +6,7 @@ updated: 2021-02-05 ## Objective -The [OVH Load Balancer](https://www.ovh.com/sg/solutions/load-balancer/){.external} service offers a number of ways of tracking connections to your services. +The [OVH Load Balancer](https://www.ovh.com/sg/solutions/load-balancer/) service offers a number of ways of tracking connections to your services. Each session on the OVH Load Balancer service is maintained by a persistent connection system. The system is configured on the application layer of the OVH Load Balancer service, and it maintains a persistent connection to the server. @@ -16,8 +16,8 @@ This guide provides an introduction to the ways in which you can configure these ## Requirements -- an [OVH Load Balancer](https://www.ovh.com/sg/solutions/load-balancer/){.external} -- access to the [OVH Control Panel](/links/manager){.external}, or the [OVH API](/links/api){.external} +- an [OVH Load Balancer](https://www.ovh.com/sg/solutions/load-balancer/) +- access to the [OVH Control Panel](/links/manager), or the [OVH API](/links/api) ## Instructions diff --git a/pages/network/load_balancer/create_stickiness/guide.en-us.md b/pages/network/load_balancer/create_stickiness/guide.en-us.md index ebf38b2ec7a..ba1f010c776 100644 --- a/pages/network/load_balancer/create_stickiness/guide.en-us.md +++ b/pages/network/load_balancer/create_stickiness/guide.en-us.md @@ -6,7 +6,7 @@ updated: 2021-02-05 ## Objective -The [OVH Load Balancer](https://www.ovh.com/world/solutions/load-balancer/){.external} service offers a number of ways of tracking connections to your services. +The [OVH Load Balancer](https://www.ovh.com/world/solutions/load-balancer/) service offers a number of ways of tracking connections to your services. Each session on the OVH Load Balancer service is maintained by a persistent connection system. The system is configured on the application layer of the OVH Load Balancer service, and it maintains a persistent connection to the server. @@ -16,8 +16,8 @@ This guide provides an introduction to the ways in which you can configure these ## Requirements -- an [OVH Load Balancer](https://www.ovh.com/world/solutions/load-balancer/){.external} -- access to the [OVH Control Panel](/links/manager){.external}, or the [OVH API](/links/api){.external} +- an [OVH Load Balancer](https://www.ovh.com/world/solutions/load-balancer/) +- access to the [OVH Control Panel](/links/manager), or the [OVH API](/links/api) ## Instructions diff --git a/pages/network/load_balancer/create_stickiness/guide.fr-ca.md b/pages/network/load_balancer/create_stickiness/guide.fr-ca.md index ec780217e80..2c71161498d 100644 --- a/pages/network/load_balancer/create_stickiness/guide.fr-ca.md +++ b/pages/network/load_balancer/create_stickiness/guide.fr-ca.md @@ -6,7 +6,7 @@ updated: 2021-02-05 ## Objectif -Le service [Load Balancer OVH](https://www.ovh.com/ca/fr/solutions/load-balancer/){.external} offre différents types de suivi de connexion pour vos services. +Le service [Load Balancer OVH](https://www.ovh.com/ca/fr/solutions/load-balancer/) offre différents types de suivi de connexion pour vos services. Chaque session du service OVH Load Balancer est maintenue par un système de persistence de connexion. Ce dernier est configuré au niveau de la couche applicative du service OVH Load Balancer, c'est elle qui assure la persistence de la connexion vers le serveur. @@ -16,10 +16,10 @@ Cette documentation présente différentes façon de configurer cette options po ## Prérequis -- Disposer d'un [Load Balancer OVH](https://www.ovh.com/ca/fr/solutions/load-balancer/){.external}. +- Disposer d'un [Load Balancer OVH](https://www.ovh.com/ca/fr/solutions/load-balancer/). - Avoir accès : - - à l'[espace client OVH](/links/manager){.external}, ou bien - - à l'[API OVH](/links/api){.external}. + - à l'[espace client OVH](/links/manager), ou bien + - à l'[API OVH](/links/api). ## En pratique diff --git a/pages/network/load_balancer/create_stickiness/guide.fr-fr.md b/pages/network/load_balancer/create_stickiness/guide.fr-fr.md index 4088bd517a3..57f4943504e 100644 --- a/pages/network/load_balancer/create_stickiness/guide.fr-fr.md +++ b/pages/network/load_balancer/create_stickiness/guide.fr-fr.md @@ -6,7 +6,7 @@ updated: 2022-03-28 ## Objectif -Le service [Load Balancer OVHcloud](/links/network/load-balancer){.external} offre différents types de suivi de connexion pour vos services. +Le service [Load Balancer OVHcloud](/links/network/load-balancer) offre différents types de suivi de connexion pour vos services. Chaque session du service OVHcloud Load Balancer est maintenue par un système de persistence de connexion. Ce dernier est configuré au niveau de la couche applicative du service OVHcloud Load Balancer, c'est elle qui assure la persistence de la connexion vers le serveur. @@ -14,9 +14,9 @@ Chaque session du service OVHcloud Load Balancer est maintenue par un système d ## Prérequis -- Disposer d'un [Load Balancer OVHcloud](/links/network/load-balancer){.external}. -- Avoir accès à l'[espace client OVHcloud](/links/manager){.external}, ou bien -- Avoir accès à l'[API OVHcloud](/links/api){.external}. +- Disposer d'un [Load Balancer OVHcloud](/links/network/load-balancer). +- Avoir accès à l'[espace client OVHcloud](/links/manager), ou bien +- Avoir accès à l'[API OVHcloud](/links/api). ## En pratique @@ -42,7 +42,7 @@ Les éléments suivants auront un impact sur la redirection de trafic : ### Modifier le mode de suivi de connexion d'une ferme via l'espace client OVHcloud -Dans l'[espace client OVHcloud](/links/manager){.external} rendez-vous dans la partie `Bare Metal Cloud`{.action} puis `Load Balancer`{.action}. +Dans l'[espace client OVHcloud](/links/manager) rendez-vous dans la partie `Bare Metal Cloud`{.action} puis `Load Balancer`{.action}. Pour modifier le suivi de connexion d'une ferme, il faut éditer celle-ci en allant dans l'onglet `Ferme de serveurs`{.action} puis cliquez sur le bouton d'édition `...`{.action} à droite de la ferme voulue et sélectionnez `Modifier`{.action}. diff --git a/pages/network/load_balancer/howto_route_ipfo/guide.en-asia.md b/pages/network/load_balancer/howto_route_ipfo/guide.en-asia.md index 2f2a1f7ea54..3b6afd7d05f 100644 --- a/pages/network/load_balancer/howto_route_ipfo/guide.en-asia.md +++ b/pages/network/load_balancer/howto_route_ipfo/guide.en-asia.md @@ -13,18 +13,18 @@ updated: 2022-10-06 An Additional IP is an IP address that can be switched from one service to another. In doing so, it helps you avoid a wide range of issues for your infrastructure (hardware failures, overload for your services, maintenance, etc.). -For more information on Additional IPs, you can consult our [webpage](/links/bare-metal/ip){.external}. +For more information on Additional IPs, you can consult our [webpage](/links/bare-metal/ip). The OVH Load Balancer solution offers load balancing features for a range of different protocols: HTTP, HTTPS, TCP and UDP. When you link it to an Additional IP, you can switch over your existing infrastructure to a Load Balancer without disturbing or interrupting services for your customers. Effectively, you will not need to change the IP address any longer if you are still using the Additional IP, so you will not need to wait for your DNS zone to propagate any changes. -For more information on the OVH Load Balancer solution, you can read our [Introduction to the OVH Load Balancer](/pages/network/load_balancer/use_presentation){.external}. +For more information on the OVH Load Balancer solution, you can read our [Introduction to the OVH Load Balancer](/pages/network/load_balancer/use_presentation). **This guide will explain how to use the Additional IP with the OVH Load Balancer service.** ## Requirements -- a correctly configured [OVH Load Balancer](https://www.ovh.com/asia/solutions/load-balancer/){.external} -- an [Additional IP](/links/bare-metal/ip){.external} +- a correctly configured [OVH Load Balancer](https://www.ovh.com/asia/solutions/load-balancer/) +- an [Additional IP](/links/bare-metal/ip) > [!primary] > @@ -51,7 +51,7 @@ In this document, we will look at two distinct uses: ### Add an Additional IP. -You can link these IPs to your OVH Load Balancer via the [OVH API](https://ca.api.ovh.com){.external}. +You can link these IPs to your OVH Load Balancer via the [OVH API](https://ca.api.ovh.com). The API call for this is as follows: > [!api] @@ -76,7 +76,7 @@ No matter what kind of front-end you wish to use, you can define a list of dedic #### If you are creating a front-end: -From the [OVH API](https://ca.api.ovh.com){.external}, you can use the following call to define one or more Additional IPs on a front-end as you create it: +From the [OVH API](https://ca.api.ovh.com), you can use the following call to define one or more Additional IPs on a front-end as you create it: * HTTP protocol @@ -101,7 +101,7 @@ From the [OVH API](https://ca.api.ovh.com){.external}, you can use the following #### If you are updating an existing front-end: -From the [OVH API](https://ca.api.ovh.com){.external}, you can use the following call to define one or more Additional IPs on an existing front-end: +From the [OVH API](https://ca.api.ovh.com), you can use the following call to define one or more Additional IPs on an existing front-end: * HTTP protocol @@ -126,7 +126,7 @@ From the [OVH API](https://ca.api.ovh.com){.external}, you can use the following ### Via the OVH Control Panel. -You can define dedicated Additional IPs via the [OVH Control Panel](/links/manager){.external} by going to the `Cloud`{.action} section, then `Load Balancer`{.action}. +You can define dedicated Additional IPs via the [OVH Control Panel](/links/manager) by going to the `Cloud`{.action} section, then `Load Balancer`{.action}. Once you have selected the Load Balancer you want to modify, create a new front-end, or edit an existing one. diff --git a/pages/network/load_balancer/howto_route_ipfo/guide.en-au.md b/pages/network/load_balancer/howto_route_ipfo/guide.en-au.md index a8acffb2dd4..335d0a87dcd 100644 --- a/pages/network/load_balancer/howto_route_ipfo/guide.en-au.md +++ b/pages/network/load_balancer/howto_route_ipfo/guide.en-au.md @@ -13,18 +13,18 @@ updated: 2022-10-06 An Additional IP is an IP address that can be switched from one service to another. In doing so, it helps you avoid a wide range of issues for your infrastructure (hardware failures, overload for your services, maintenance, etc.). -For more information on Additional IPs, you can consult our [webpage](/links/bare-metal/ip){.external}. +For more information on Additional IPs, you can consult our [webpage](/links/bare-metal/ip). The OVH Load Balancer solution offers load balancing features for a range of different protocols: HTTP, HTTPS, TCP and UDP. When you link it to an Additional IP, you can switch over your existing infrastructure to a Load Balancer without disturbing or interrupting services for your customers. Effectively, you will not need to change the IP address any longer if you are still using the Additional IP, so you will not need to wait for your DNS zone to propagate any changes. -For more information on the OVH Load Balancer solution, you can read our [Introduction to the OVH Load Balancer](/pages/network/load_balancer/use_presentation){.external}. +For more information on the OVH Load Balancer solution, you can read our [Introduction to the OVH Load Balancer](/pages/network/load_balancer/use_presentation). **This guide will explain how to use the Additional IP with the OVH Load Balancer service.** ## Requirements -- a correctly configured [OVH Load Balancer](https://www.ovh.com.au/solutions/load-balancer/){.external} -- an [Additional IP](/links/bare-metal/ip){.external} +- a correctly configured [OVH Load Balancer](https://www.ovh.com.au/solutions/load-balancer/) +- an [Additional IP](/links/bare-metal/ip) > [!primary] > @@ -51,7 +51,7 @@ In this document, we will look at two distinct uses: ### Add an Additional IP. -You can link these IPs to your OVH Load Balancer via the [OVH API](https://ca.api.ovh.com){.external}. +You can link these IPs to your OVH Load Balancer via the [OVH API](https://ca.api.ovh.com). The API call for this is as follows: > [!api] @@ -76,7 +76,7 @@ No matter what kind of front-end you wish to use, you can define a list of dedic #### If you are creating a front-end: -From the [OVH API](https://ca.api.ovh.com){.external}, you can use the following call to define one or more Additional IPs on a front-end as you create it: +From the [OVH API](https://ca.api.ovh.com), you can use the following call to define one or more Additional IPs on a front-end as you create it: * HTTP protocol @@ -101,7 +101,7 @@ From the [OVH API](https://ca.api.ovh.com){.external}, you can use the following #### If you are updating an existing front-end: -From the [OVH API](https://ca.api.ovh.com){.external}, you can use the following call to define one or more Additional IPs on an existing front-end: +From the [OVH API](https://ca.api.ovh.com), you can use the following call to define one or more Additional IPs on an existing front-end: * HTTP protocol @@ -126,7 +126,7 @@ From the [OVH API](https://ca.api.ovh.com){.external}, you can use the following ### Via the OVH Control Panel. -You can define dedicated Additional IPs via the [OVH Control Panel](/links/manager){.external} by going to the `Cloud`{.action} section, then `Load Balancer`{.action}. +You can define dedicated Additional IPs via the [OVH Control Panel](/links/manager) by going to the `Cloud`{.action} section, then `Load Balancer`{.action}. Once you have selected the Load Balancer you want to modify, create a new front-end, or edit an existing one. diff --git a/pages/network/load_balancer/howto_route_ipfo/guide.en-ca.md b/pages/network/load_balancer/howto_route_ipfo/guide.en-ca.md index c95b9fbc0ad..0acb56555c6 100644 --- a/pages/network/load_balancer/howto_route_ipfo/guide.en-ca.md +++ b/pages/network/load_balancer/howto_route_ipfo/guide.en-ca.md @@ -13,18 +13,18 @@ updated: 2022-10-06 An Additional IP is an IP address that can be switched from one service to another. In doing so, it helps you avoid a wide range of issues for your infrastructure (hardware failures, overload for your services, maintenance, etc.). -For more information on Additional IPs, you can consult our [webpage](/links/bare-metal/ip){.external}. +For more information on Additional IPs, you can consult our [webpage](/links/bare-metal/ip). The OVH Load Balancer solution offers load balancing features for a range of different protocols: HTTP, HTTPS, TCP and UDP. When you link it to an Additional IP, you can switch over your existing infrastructure to a Load Balancer without disturbing or interrupting services for your customers. Effectively, you will not need to change the IP address any longer if you are still using the Additional IP, so you will not need to wait for your DNS zone to propagate any changes. -For more information on the OVH Load Balancer solution, you can read our [Introduction to the OVH Load Balancer](/pages/network/load_balancer/use_presentation){.external}. +For more information on the OVH Load Balancer solution, you can read our [Introduction to the OVH Load Balancer](/pages/network/load_balancer/use_presentation). **This guide will explain how to use the Additional IP with the OVH Load Balancer service.** ## Requirements -- a correctly configured [OVH Load Balancer](https://www.ovh.com/ca/en/solutions/load-balancer/){.external} -- an [Additional IP](/links/bare-metal/ip){.external} +- a correctly configured [OVH Load Balancer](https://www.ovh.com/ca/en/solutions/load-balancer/) +- an [Additional IP](/links/bare-metal/ip) > [!primary] > @@ -51,7 +51,7 @@ In this document, we will look at two distinct uses: ### Add an Additional IP. -You can link these IPs to your OVH Load Balancer via the [OVH API](https://ca.api.ovh.com){.external}. +You can link these IPs to your OVH Load Balancer via the [OVH API](https://ca.api.ovh.com). The API call for this is as follows: > [!api] @@ -76,7 +76,7 @@ No matter what kind of front-end you wish to use, you can define a list of dedic #### If you are creating a front-end: -From the [OVH API](https://ca.api.ovh.com){.external}, you can use the following call to define one or more Additional IPs on a front-end as you create it: +From the [OVH API](https://ca.api.ovh.com), you can use the following call to define one or more Additional IPs on a front-end as you create it: * HTTP protocol @@ -101,7 +101,7 @@ From the [OVH API](https://ca.api.ovh.com){.external}, you can use the following #### If you are updating an existing front-end: -From the [OVH API](https://ca.api.ovh.com){.external}, you can use the following call to define one or more Additional IPs on an existing front-end: +From the [OVH API](https://ca.api.ovh.com), you can use the following call to define one or more Additional IPs on an existing front-end: * HTTP protocol @@ -126,7 +126,7 @@ From the [OVH API](https://ca.api.ovh.com){.external}, you can use the following ### Via the OVH Control Panel. -You can define dedicated Additional IPs via the [OVH Control Panel](/links/manager){.external} by going to the `Cloud`{.action} section, then `Load Balancer`{.action}. +You can define dedicated Additional IPs via the [OVH Control Panel](/links/manager) by going to the `Cloud`{.action} section, then `Load Balancer`{.action}. Once you have selected the Load Balancer you want to modify, create a new front-end, or edit an existing one. diff --git a/pages/network/load_balancer/howto_route_ipfo/guide.en-gb.md b/pages/network/load_balancer/howto_route_ipfo/guide.en-gb.md index 4e4712c64bd..8ff098aa8c5 100644 --- a/pages/network/load_balancer/howto_route_ipfo/guide.en-gb.md +++ b/pages/network/load_balancer/howto_route_ipfo/guide.en-gb.md @@ -13,18 +13,18 @@ updated: 2022-10-06 An Additional IP is an IP address that can be switched from one service to another. In doing so, it helps you avoid a wide range of issues for your infrastructure (hardware failures, overload for your services, maintenance, etc.). -For more information on Additional IPs, you can consult our [webpage](/links/bare-metal/ip){.external}. +For more information on Additional IPs, you can consult our [webpage](/links/bare-metal/ip). The OVH Load Balancer solution offers load balancing features for a range of different protocols: HTTP, HTTPS, TCP and UDP. When you link it to an Additional IP, you can switch over your existing infrastructure to a Load Balancer without disturbing or interrupting services for your customers. Effectively, you will not need to change the IP address any longer if you are still using the Additional IP, so you will not need to wait for your DNS zone to propagate any changes. -For more information on the OVH Load Balancer solution, you can read our [Introduction to the OVH Load Balancer](/pages/network/load_balancer/use_presentation){.external}. +For more information on the OVH Load Balancer solution, you can read our [Introduction to the OVH Load Balancer](/pages/network/load_balancer/use_presentation). **This guide will explain how to use the Additional IP with the OVH Load Balancer service.** ## Requirements -- a correctly configured [OVH Load Balancer](/links/network/load-balancer){.external} -- an [Additional IP](/links/bare-metal/ip){.external} +- a correctly configured [OVH Load Balancer](/links/network/load-balancer) +- an [Additional IP](/links/bare-metal/ip) > [!primary] > @@ -51,7 +51,7 @@ In this document, we will look at two distinct uses: ### Add an Additional IP. -You can link these IPs to your OVH Load Balancer via the [OVH API](https://api.ovh.com){.external}. +You can link these IPs to your OVH Load Balancer via the [OVH API](https://api.ovh.com). The API call for this is as follows: > [!api] @@ -76,7 +76,7 @@ No matter what kind of front-end you wish to use, you can define a list of dedic #### If you are creating a front-end: -From the [OVH API](https://api.ovh.com){.external}, you can use the following call to define one or more Additional IPs on a front-end as you create it: +From the [OVH API](https://api.ovh.com), you can use the following call to define one or more Additional IPs on a front-end as you create it: * HTTP protocol @@ -101,7 +101,7 @@ From the [OVH API](https://api.ovh.com){.external}, you can use the following ca #### If you are updating an existing front-end: -From the [OVH API](https://api.ovh.com){.external}, you can use the following call to define one or more Additional IPs on an existing front-end: +From the [OVH API](https://api.ovh.com), you can use the following call to define one or more Additional IPs on an existing front-end: * HTTP protocol @@ -126,7 +126,7 @@ From the [OVH API](https://api.ovh.com){.external}, you can use the following ca ### Via the OVH Control Panel. -You can define dedicated Additional IPs via the [OVH Control Panel](/links/manager){.external} by going to the `Cloud`{.action} section, then `Load Balancer`{.action}. +You can define dedicated Additional IPs via the [OVH Control Panel](/links/manager) by going to the `Cloud`{.action} section, then `Load Balancer`{.action}. Once you have selected the Load Balancer you want to modify, create a new front-end, or edit an existing one. diff --git a/pages/network/load_balancer/howto_route_ipfo/guide.en-sg.md b/pages/network/load_balancer/howto_route_ipfo/guide.en-sg.md index e32b1c08fcc..9900b5b2169 100644 --- a/pages/network/load_balancer/howto_route_ipfo/guide.en-sg.md +++ b/pages/network/load_balancer/howto_route_ipfo/guide.en-sg.md @@ -13,18 +13,18 @@ updated: 2022-10-06 An Additional IP is an IP address that can be switched from one service to another. In doing so, it helps you avoid a wide range of issues for your infrastructure (hardware failures, overload for your services, maintenance, etc.). -For more information on Additional IPs, you can consult our [webpage](/links/bare-metal/ip){.external}. +For more information on Additional IPs, you can consult our [webpage](/links/bare-metal/ip). The OVH Load Balancer solution offers load balancing features for a range of different protocols: HTTP, HTTPS, TCP and UDP. When you link it to an Additional IP, you can switch over your existing infrastructure to a Load Balancer without disturbing or interrupting services for your customers. Effectively, you will not need to change the IP address any longer if you are still using the Additional IP, so you will not need to wait for your DNS zone to propagate any changes. -For more information on the OVH Load Balancer solution, you can read our [Introduction to the OVH Load Balancer](/pages/network/load_balancer/use_presentation){.external}. +For more information on the OVH Load Balancer solution, you can read our [Introduction to the OVH Load Balancer](/pages/network/load_balancer/use_presentation). **This guide will explain how to use the Additional IP with the OVH Load Balancer service.** ## Requirements -- a correctly configured [OVH Load Balancer](https://www.ovh.com/sg/solutions/load-balancer/){.external} -- an [Additional IP](/links/bare-metal/ip){.external} +- a correctly configured [OVH Load Balancer](https://www.ovh.com/sg/solutions/load-balancer/) +- an [Additional IP](/links/bare-metal/ip) > [!primary] > @@ -51,7 +51,7 @@ In this document, we will look at two distinct uses: ### Add an Additional IP. -You can link these IPs to your OVH Load Balancer via the [OVH API](https://ca.api.ovh.com){.external}. +You can link these IPs to your OVH Load Balancer via the [OVH API](https://ca.api.ovh.com). The API call for this is as follows: > [!api] @@ -76,7 +76,7 @@ No matter what kind of front-end you wish to use, you can define a list of dedic #### If you are creating a front-end: -From the [OVH API](https://ca.api.ovh.com){.external}, you can use the following call to define one or more Additional IPs on a front-end as you create it: +From the [OVH API](https://ca.api.ovh.com), you can use the following call to define one or more Additional IPs on a front-end as you create it: * HTTP protocol @@ -101,7 +101,7 @@ From the [OVH API](https://ca.api.ovh.com){.external}, you can use the following #### If you are updating an existing front-end: -From the [OVH API](https://ca.api.ovh.com){.external}, you can use the following call to define one or more Additional IPs on an existing front-end: +From the [OVH API](https://ca.api.ovh.com), you can use the following call to define one or more Additional IPs on an existing front-end: * HTTP protocol @@ -126,7 +126,7 @@ From the [OVH API](https://ca.api.ovh.com){.external}, you can use the following ### Via the OVH Control Panel. -You can define dedicated Additional IPs via the [OVH Control Panel](/links/manager){.external} by going to the `Cloud`{.action} section, then `Load Balancer`{.action}. +You can define dedicated Additional IPs via the [OVH Control Panel](/links/manager) by going to the `Cloud`{.action} section, then `Load Balancer`{.action}. Once you have selected the Load Balancer you want to modify, create a new front-end, or edit an existing one. diff --git a/pages/network/load_balancer/howto_route_ipfo/guide.en-us.md b/pages/network/load_balancer/howto_route_ipfo/guide.en-us.md index ede676b1881..36af4973b1a 100644 --- a/pages/network/load_balancer/howto_route_ipfo/guide.en-us.md +++ b/pages/network/load_balancer/howto_route_ipfo/guide.en-us.md @@ -13,18 +13,18 @@ updated: 2022-10-06 An Additional IP is an IP address that can be switched from one service to another. In doing so, it helps you avoid a wide range of issues for your infrastructure (hardware failures, overload for your services, maintenance, etc.). -For more information on Additional IPs, you can consult our [webpage](/links/bare-metal/ip){.external}. +For more information on Additional IPs, you can consult our [webpage](/links/bare-metal/ip). The OVH Load Balancer solution offers load balancing features for a range of different protocols: HTTP, HTTPS, TCP and UDP. When you link it to an Additional IP, you can switch over your existing infrastructure to a Load Balancer without disturbing or interrupting services for your customers. Effectively, you will not need to change the IP address any longer if you are still using the Additional IP, so you will not need to wait for your DNS zone to propagate any changes. -For more information on the OVH Load Balancer solution, you can read our [Introduction to the OVH Load Balancer](/pages/network/load_balancer/use_presentation){.external}. +For more information on the OVH Load Balancer solution, you can read our [Introduction to the OVH Load Balancer](/pages/network/load_balancer/use_presentation). **This guide will explain how to use the Additional IP with the OVH Load Balancer service.** ## Requirements -- a correctly configured [OVH Load Balancer](https://www.ovh.com/world/solutions/load-balancer/){.external} -- an [Additional IP](/links/bare-metal/ip){.external} +- a correctly configured [OVH Load Balancer](https://www.ovh.com/world/solutions/load-balancer/) +- an [Additional IP](/links/bare-metal/ip) > [!primary] > @@ -51,7 +51,7 @@ In this document, we will look at two distinct uses: ### Add an Additional IP. -You can link these IPs to your OVH Load Balancer via the [OVH API](https://ca.api.ovh.com){.external}. +You can link these IPs to your OVH Load Balancer via the [OVH API](https://ca.api.ovh.com). The API call for this is as follows: > [!api] @@ -76,7 +76,7 @@ No matter what kind of front-end you wish to use, you can define a list of dedic #### If you are creating a front-end: -From the [OVH API](https://ca.api.ovh.com){.external}, you can use the following call to define one or more Additional IPs on a front-end as you create it: +From the [OVH API](https://ca.api.ovh.com), you can use the following call to define one or more Additional IPs on a front-end as you create it: * HTTP protocol @@ -101,7 +101,7 @@ From the [OVH API](https://ca.api.ovh.com){.external}, you can use the following #### If you are updating an existing front-end: -From the [OVH API](https://ca.api.ovh.com){.external}, you can use the following call to define one or more Additional IPs on an existing front-end: +From the [OVH API](https://ca.api.ovh.com), you can use the following call to define one or more Additional IPs on an existing front-end: * HTTP protocol @@ -126,7 +126,7 @@ From the [OVH API](https://ca.api.ovh.com){.external}, you can use the following ### Via the OVH Control Panel. -You can define dedicated Additional IPs via the [OVH Control Panel](/links/manager){.external} by going to the `Cloud`{.action} section, then `Load Balancer`{.action}. +You can define dedicated Additional IPs via the [OVH Control Panel](/links/manager) by going to the `Cloud`{.action} section, then `Load Balancer`{.action}. Once you have selected the Load Balancer you want to modify, create a new front-end, or edit an existing one. diff --git a/pages/network/load_balancer/howto_route_ipfo/guide.fr-ca.md b/pages/network/load_balancer/howto_route_ipfo/guide.fr-ca.md index 49778fa5df9..159af599fcb 100644 --- a/pages/network/load_balancer/howto_route_ipfo/guide.fr-ca.md +++ b/pages/network/load_balancer/howto_route_ipfo/guide.fr-ca.md @@ -13,18 +13,18 @@ updated: 2022-10-06 Une Additional IP est une adresse IP basculable d'un service à l'autre. Elle offre donc la possibilité de disposer d'une infrastructure résistant à une grande diversité de problèmes (pannes matérielles, surcharges de vos services, maintenance...). -Pour plus d'informations sur l'Additional IP nous vous recommandons la lecture du [document de présentation](/links/bare-metal/ip){.external}. +Pour plus d'informations sur l'Additional IP nous vous recommandons la lecture du [document de présentation](/links/bare-metal/ip). Le service OVH Load Balancer offre quant à lui des fonctionnalités de répartition de charge sur différents protocoles : HTTP, HTTPS, TCP et UDP. Associé à une Additional IP, il devient possible de basculer votre infrastructure existante vers un Load Balancer sans perturber ou interrompre les services de vos clients. En effet il n'y aura désormais plus de changement d'adresse IP dans la mesure où vous utiliserez toujours l'Additional IP, donc pas de délai de propagation des DNS. -Pour plus d'informations sur le service OVH Load Balancer, nous vous conseillons de consulter la [présentation générale](/pages/network/load_balancer/use_presentation){.external}. +Pour plus d'informations sur le service OVH Load Balancer, nous vous conseillons de consulter la [présentation générale](/pages/network/load_balancer/use_presentation). **Ce guide vous explique comment utiliser une Additional IP avec le service OVH Load Balancer.** ## Prérequis -- Disposer d'un [Load Balancer OVH](https://www.ovh.com/ca/fr/solutions/load-balancer/){.external} correctement configuré. -- Disposer d'une [Additional IP](/links/bare-metal/ip){.external}. +- Disposer d'un [Load Balancer OVH](https://www.ovh.com/ca/fr/solutions/load-balancer/) correctement configuré. +- Disposer d'une [Additional IP](/links/bare-metal/ip). > [!primary] > @@ -50,7 +50,7 @@ Dans la suite de ce document, nous allons voir 2 cas d'usages distincts. - Associer une Additional IP à un seul et unique frontend de votre service OVH Load Balancer. ### Ajouter une Additional IP -Depuis l'[API OVH](https://ca.api.ovh.com){.external} vous pouvez associer ces IPs avec votre service OVH Load Balancer. +Depuis l'[API OVH](https://ca.api.ovh.com) vous pouvez associer ces IPs avec votre service OVH Load Balancer. Voici l'appel API pour cela : > [!api] @@ -78,7 +78,7 @@ Les services de vos autres frontends restent quant à eux accessibles via l'adre #### Création d'un Frontend -Depuis l'[API OVH](https://ca.api.ovh.com){.external}, l'appel suivant vous permettra de définir une ou plusieurs Additional IPss sur un frontend pendant sa création : +Depuis l'[API OVH](https://ca.api.ovh.com), l'appel suivant vous permettra de définir une ou plusieurs Additional IPss sur un frontend pendant sa création : * protocole HTTP @@ -103,7 +103,7 @@ Depuis l'[API OVH](https://ca.api.ovh.com){.external}, l'appel suivant vous perm #### Mise à jour d'un Frontend -Toujours depuis l'[API OVH](https://ca.api.ovh.com){.external}, l'appel suivant vous permettra de définir une ou plusieurs Additional IPss sur un frontend existant : +Toujours depuis l'[API OVH](https://ca.api.ovh.com), l'appel suivant vous permettra de définir une ou plusieurs Additional IPss sur un frontend existant : * protocole HTTP @@ -127,7 +127,7 @@ Toujours depuis l'[API OVH](https://ca.api.ovh.com){.external}, l'appel suivant > ### Depuis le Manager -Il est enfin possible de définir vos Additional IPs dédiées depuis l'[espace client](/links/manager){.external} dans la partie `Cloud`{.action}, section `Load Balancer`{.action}. +Il est enfin possible de définir vos Additional IPs dédiées depuis l'[espace client](/links/manager) dans la partie `Cloud`{.action}, section `Load Balancer`{.action}. Après avoir sélectionné le Load Balancer que vous souhaitez modifier, créez un nouveau Frontend, ou éditez en un existants. diff --git a/pages/network/load_balancer/howto_route_ipfo/guide.fr-fr.md b/pages/network/load_balancer/howto_route_ipfo/guide.fr-fr.md index 9b5e7a90b7b..090b76827ca 100644 --- a/pages/network/load_balancer/howto_route_ipfo/guide.fr-fr.md +++ b/pages/network/load_balancer/howto_route_ipfo/guide.fr-fr.md @@ -51,7 +51,7 @@ Dans la suite de ce document, nous allons voir 2 cas d'usages distincts. ### Ajouter une Additional IP -Depuis l'[API OVHcloud](https://api.ovh.com){.external}, vous pouvez associer ces IPs avec votre service OVHcloud Load Balancer. +Depuis l'[API OVHcloud](https://api.ovh.com), vous pouvez associer ces IPs avec votre service OVHcloud Load Balancer. Voici l'appel API pour cela : @@ -81,7 +81,7 @@ Les services de vos autres frontends restent quant à eux accessibles via l'adre ##### **Création d'un frontend** -Depuis l'[API OVHcloud](https://api.ovh.com){.external}, l'appel suivant vous permettra de définir une ou plusieurs Additional IPs sur un frontend pendant sa création : +Depuis l'[API OVHcloud](https://api.ovh.com), l'appel suivant vous permettra de définir une ou plusieurs Additional IPs sur un frontend pendant sa création : - protocole HTTP @@ -106,7 +106,7 @@ Depuis l'[API OVHcloud](https://api.ovh.com){.external}, l'appel suivant vous pe ##### **Mise à jour d'un frontend** -Toujours depuis l'[API OVHcloud](https://api.ovh.com){.external}, l'appel suivant vous permettra de définir une ou plusieurs Additional IPs sur un frontend existant : +Toujours depuis l'[API OVHcloud](https://api.ovh.com), l'appel suivant vous permettra de définir une ou plusieurs Additional IPs sur un frontend existant : - protocole HTTP @@ -131,7 +131,7 @@ Toujours depuis l'[API OVHcloud](https://api.ovh.com){.external}, l'appel suivan #### Depuis l'espace client OVHcloud -Vous pouvez définir vos Additional IPs dédiées depuis l'[espace client OVHcloud](/links/manager){.external}. Rendez-vous dans la partie `Bare metal Cloud`{.action} puis dans `Load Balancer`{.action}. +Vous pouvez définir vos Additional IPs dédiées depuis l'[espace client OVHcloud](/links/manager). Rendez-vous dans la partie `Bare metal Cloud`{.action} puis dans `Load Balancer`{.action}. Après avoir sélectionné le Load Balancer que vous souhaitez modifier, créez un nouveau frontend, ou éditez-en un existant. diff --git a/pages/network/load_balancer/order_freecertificate/guide.fr-fr.md b/pages/network/load_balancer/order_freecertificate/guide.fr-fr.md index 0c9766d550b..0922f947f32 100644 --- a/pages/network/load_balancer/order_freecertificate/guide.fr-fr.md +++ b/pages/network/load_balancer/order_freecertificate/guide.fr-fr.md @@ -25,7 +25,7 @@ Par ailleurs, tous vos certificats sont ainsi centralisés au même endroit et l La première étape est de configurer votre frontend pour gérer la terminaison SSL. -Vous pouvez configurer votre terminaison SSL depuis l'[espace client OVHcloud](/links/manager){.external} dans la partie `Bare Metal Cloud`{.action} puis `Load Balancer`{.action}. +Vous pouvez configurer votre terminaison SSL depuis l'[espace client OVHcloud](/links/manager) dans la partie `Bare Metal Cloud`{.action} puis `Load Balancer`{.action}. Après avoir sélectionné le Load Balancer que vous souhaitez modifier, créez un nouveau frontend ou éditez-en un existant. diff --git a/pages/network/load_balancer/retrieve_servers_state/guide.fr-fr.md b/pages/network/load_balancer/retrieve_servers_state/guide.fr-fr.md index c963eb29e86..0d0e6310725 100644 --- a/pages/network/load_balancer/retrieve_servers_state/guide.fr-fr.md +++ b/pages/network/load_balancer/retrieve_servers_state/guide.fr-fr.md @@ -22,7 +22,7 @@ Ce tutoriel explique comment connaître l'état de santé de chaque serveur pour - Posséder une offre [OVHcloud Load balancer](/links/network/load-balancer) dans votre compte OVHcloud. - Être connecté à votre [espace client OVHcloud](/links/manager). -- Être connecté à l'[API OVHcloud](/links/api){.external}. +- Être connecté à l'[API OVHcloud](/links/api). - Posséder une ferme configurée - Posséder un frontend configuré diff --git a/pages/network/load_balancer/use_api_details/guide.en-asia.md b/pages/network/load_balancer/use_api_details/guide.en-asia.md index 8911c46e25b..d02d2004668 100644 --- a/pages/network/load_balancer/use_api_details/guide.en-asia.md +++ b/pages/network/load_balancer/use_api_details/guide.en-asia.md @@ -16,7 +16,7 @@ Description of the different input points in the API for the Load Balancer OVH. Details of the API functionality for the Load Balancer OVH -- All API calls are made in the section */ipLoadbalancing* available here : [https://ca.api.ovh.com/console/#/ipLoadbalancing](https://ca.api.ovh.com/console/#/ipLoadbalancing){.external}. +- All API calls are made in the section */ipLoadbalancing* available here : [https://ca.api.ovh.com/console/#/ipLoadbalancing](https://ca.api.ovh.com/console/#/ipLoadbalancing). > [!warning] > diff --git a/pages/network/load_balancer/use_api_details/guide.en-au.md b/pages/network/load_balancer/use_api_details/guide.en-au.md index 8911c46e25b..d02d2004668 100644 --- a/pages/network/load_balancer/use_api_details/guide.en-au.md +++ b/pages/network/load_balancer/use_api_details/guide.en-au.md @@ -16,7 +16,7 @@ Description of the different input points in the API for the Load Balancer OVH. Details of the API functionality for the Load Balancer OVH -- All API calls are made in the section */ipLoadbalancing* available here : [https://ca.api.ovh.com/console/#/ipLoadbalancing](https://ca.api.ovh.com/console/#/ipLoadbalancing){.external}. +- All API calls are made in the section */ipLoadbalancing* available here : [https://ca.api.ovh.com/console/#/ipLoadbalancing](https://ca.api.ovh.com/console/#/ipLoadbalancing). > [!warning] > diff --git a/pages/network/load_balancer/use_api_details/guide.en-ca.md b/pages/network/load_balancer/use_api_details/guide.en-ca.md index 8911c46e25b..d02d2004668 100644 --- a/pages/network/load_balancer/use_api_details/guide.en-ca.md +++ b/pages/network/load_balancer/use_api_details/guide.en-ca.md @@ -16,7 +16,7 @@ Description of the different input points in the API for the Load Balancer OVH. Details of the API functionality for the Load Balancer OVH -- All API calls are made in the section */ipLoadbalancing* available here : [https://ca.api.ovh.com/console/#/ipLoadbalancing](https://ca.api.ovh.com/console/#/ipLoadbalancing){.external}. +- All API calls are made in the section */ipLoadbalancing* available here : [https://ca.api.ovh.com/console/#/ipLoadbalancing](https://ca.api.ovh.com/console/#/ipLoadbalancing). > [!warning] > diff --git a/pages/network/load_balancer/use_api_details/guide.en-gb.md b/pages/network/load_balancer/use_api_details/guide.en-gb.md index 37e0920ab0d..d90a129d77b 100644 --- a/pages/network/load_balancer/use_api_details/guide.en-gb.md +++ b/pages/network/load_balancer/use_api_details/guide.en-gb.md @@ -16,7 +16,7 @@ Description of the different input points in the API for the Load Balancer OVH. Details of the API functionality for the Load Balancer OVH -- All API calls are made in the section */ipLoadbalancing* available here : [https://api.ovh.com/console/#/ipLoadbalancing](https://api.ovh.com/console/#/ipLoadbalancing){.external}. +- All API calls are made in the section */ipLoadbalancing* available here : [https://api.ovh.com/console/#/ipLoadbalancing](https://api.ovh.com/console/#/ipLoadbalancing). > [!warning] > diff --git a/pages/network/load_balancer/use_api_details/guide.en-sg.md b/pages/network/load_balancer/use_api_details/guide.en-sg.md index 8911c46e25b..d02d2004668 100644 --- a/pages/network/load_balancer/use_api_details/guide.en-sg.md +++ b/pages/network/load_balancer/use_api_details/guide.en-sg.md @@ -16,7 +16,7 @@ Description of the different input points in the API for the Load Balancer OVH. Details of the API functionality for the Load Balancer OVH -- All API calls are made in the section */ipLoadbalancing* available here : [https://ca.api.ovh.com/console/#/ipLoadbalancing](https://ca.api.ovh.com/console/#/ipLoadbalancing){.external}. +- All API calls are made in the section */ipLoadbalancing* available here : [https://ca.api.ovh.com/console/#/ipLoadbalancing](https://ca.api.ovh.com/console/#/ipLoadbalancing). > [!warning] > diff --git a/pages/network/load_balancer/use_api_details/guide.en-us.md b/pages/network/load_balancer/use_api_details/guide.en-us.md index 8911c46e25b..d02d2004668 100644 --- a/pages/network/load_balancer/use_api_details/guide.en-us.md +++ b/pages/network/load_balancer/use_api_details/guide.en-us.md @@ -16,7 +16,7 @@ Description of the different input points in the API for the Load Balancer OVH. Details of the API functionality for the Load Balancer OVH -- All API calls are made in the section */ipLoadbalancing* available here : [https://ca.api.ovh.com/console/#/ipLoadbalancing](https://ca.api.ovh.com/console/#/ipLoadbalancing){.external}. +- All API calls are made in the section */ipLoadbalancing* available here : [https://ca.api.ovh.com/console/#/ipLoadbalancing](https://ca.api.ovh.com/console/#/ipLoadbalancing). > [!warning] > diff --git a/pages/network/load_balancer/use_api_details/guide.fr-ca.md b/pages/network/load_balancer/use_api_details/guide.fr-ca.md index 95aec25f392..a0ccab5b8d4 100644 --- a/pages/network/load_balancer/use_api_details/guide.fr-ca.md +++ b/pages/network/load_balancer/use_api_details/guide.fr-ca.md @@ -16,7 +16,7 @@ Description des différents points d'entrées dans l'API pour le Load Balancer O Détails des fonctionnalités de l'API pour le Load Balancer OVHcloud. -- Tous les appels API se font dans la section */ipLoadbalancing* disponible ici : [https://ca.api.ovh.com/console/#/ipLoadbalancing](https://ca.api.ovh.com/console/#/ipLoadbalancing){.external}. +- Tous les appels API se font dans la section */ipLoadbalancing* disponible ici : [https://ca.api.ovh.com/console/#/ipLoadbalancing](https://ca.api.ovh.com/console/#/ipLoadbalancing). > [!warning] > diff --git a/pages/network/load_balancer/use_api_details/guide.fr-fr.md b/pages/network/load_balancer/use_api_details/guide.fr-fr.md index fc9270ea800..a167f21323b 100644 --- a/pages/network/load_balancer/use_api_details/guide.fr-fr.md +++ b/pages/network/load_balancer/use_api_details/guide.fr-fr.md @@ -16,7 +16,7 @@ Retrouvez ici la description des différents points d'entrées dans l'API pour l ### Gérer son service OVHcloud Load Balancer via l'API -Tous les appels API se font dans la section */ipLoadbalancing* disponible ici : [https://api.ovh.com/console/#/ipLoadbalancing](https://api.ovh.com/console/#/ipLoadbalancing){.external}. +Tous les appels API se font dans la section */ipLoadbalancing* disponible ici : [https://api.ovh.com/console/#/ipLoadbalancing](https://api.ovh.com/console/#/ipLoadbalancing). > [!warning] > diff --git a/pages/network/load_balancer/use_api_logs_2_customers/guide.en-gb.md b/pages/network/load_balancer/use_api_logs_2_customers/guide.en-gb.md index 7419ddf0538..6662b67e863 100644 --- a/pages/network/load_balancer/use_api_logs_2_customers/guide.en-gb.md +++ b/pages/network/load_balancer/use_api_logs_2_customers/guide.en-gb.md @@ -42,7 +42,7 @@ If you would like to find out more about Logs Data Platform before reading this **What are the logs of an OVHcloud Load Balancer?** -The forwarded logs are generated by [HAproxy](https://en.wikipedia.org/wiki/HAProxy){.external} (the opensource component used for load balancing). +The forwarded logs are generated by [HAproxy](https://en.wikipedia.org/wiki/HAProxy) (the opensource component used for load balancing). ### Log content for TCP based listeners : `TCP`, `HTTP` @@ -61,7 +61,7 @@ The forwarded logs are generated by [HAproxy](https://en.wikipedia.org/wiki/HAPr | backend_source_port_int | Source port used by the Load Balancer to connect to your backend servers | Integer | | server_ip | IP address of the backend server connected to your Load Balancer | IP | | server_port_int | TCP port of the backend server connected to your Load Balancer | Integer | -| termination_state | The session termination indicator: 2 letters for TCP, 4 letters for HTTP, all the details on [HAProxy documentation page](https://docs.haproxy.org/2.6/configuration.html#8.5){.external}| String (e.g. "----") | +| termination_state | The session termination indicator: 2 letters for TCP, 4 letters for HTTP, all the details on [HAProxy documentation page](https://docs.haproxy.org/2.6/configuration.html#8.5)| String (e.g. "----") | | bytes_read_int | Size (in bytes) of the response sent by the Load Balancer to the client | Integer | | bytes_uploaded_int | Size (in bytes) of the request sent by the client to the Load Balancer | Integer | | time_duration_int | The duration (in milliseconds) of the TCP session at the time the request was made | Integer | @@ -185,7 +185,7 @@ Now that your logs are ingested and stored in your Logs Data Platform data strea - In the OVHcloud Control Panel, retrieve the LDP username (ex: logs-xxxx) and its password in your Logs Data Platform account home page. You can refer to the [Quick start guide for Logs Data Platform](/pages/manage_and_operate/observability/logs_data_platform/getting_started_quick_start). - Open the Graylog web-ui. You can retrieve the link in your account home page or using your Access point depending on your account region (for example: Gravelines region is https://gra1.logs.ovh.com/). - Log into Graylog using your Logs Data Platform Username and Password. -- Search through your logs across the data stream of your Logs Data Platform account. You can refer to [Graylog writing search queries](https://go2docs.graylog.org/current/making_sense_of_your_log_data/writing_search_queries.html){.external} documentation for details on search syntax. +- Search through your logs across the data stream of your Logs Data Platform account. You can refer to [Graylog writing search queries](https://go2docs.graylog.org/current/making_sense_of_your_log_data/writing_search_queries.html) documentation for details on search syntax. Refer to the following documentation: [Logs Data Platform - Visualizing, querying and exploiting your logs](/products/observability-logs-data-platform-visualizing-querying-exploiting) for more details about how to use your logs with Logs Data Platform, including how to: diff --git a/pages/network/load_balancer/use_api_logs_2_customers/guide.fr-fr.md b/pages/network/load_balancer/use_api_logs_2_customers/guide.fr-fr.md index 68cd809b51e..a4457a739dc 100644 --- a/pages/network/load_balancer/use_api_logs_2_customers/guide.fr-fr.md +++ b/pages/network/load_balancer/use_api_logs_2_customers/guide.fr-fr.md @@ -41,7 +41,7 @@ Si vous souhaitez en savoir plus sur Logs Data Platform avant de lire ce guide, **Quels sont les logs d’un OVHcloud Load Balancer ?** -Les logs transférés sont générés par [HAproxy](https://fr.wikipedia.org/wiki/HAProxy){.external} (le composant open source utilisé pour la répartition de charge). +Les logs transférés sont générés par [HAproxy](https://fr.wikipedia.org/wiki/HAProxy) (le composant open source utilisé pour la répartition de charge). ### Consignation du contenu pour les écouteurs TCP : `TCP`, `HTTP` @@ -60,7 +60,7 @@ Les logs transférés sont générés par [HAproxy](https://fr.wikipedia.org/wik | backend_source_port_int | Port source utilisé par le Load Balancer pour se connecter à vos serveurs backend | *Integer* | | server_ip | Adresse IP du serveur backend connecté à votre Load Balancer | IP | | server_port_int | Port TCP du serveur backend connecté à votre Load Balancer | *Integer* | -| termination_state | L'indicateur de fin de session : 2 lettres pour TCP, 4 lettres pour HTTP, tous les détails sont sur la [page de documentation HAProxy](https://docs.haproxy.org/2.6/configuration.html#8.5){.external}| Chaîne (par exemple « ---- ») | +| termination_state | L'indicateur de fin de session : 2 lettres pour TCP, 4 lettres pour HTTP, tous les détails sont sur la [page de documentation HAProxy](https://docs.haproxy.org/2.6/configuration.html#8.5)| Chaîne (par exemple « ---- ») | | bytes_read_int | Taille (en octets) de la réponse envoyée par le Load Balancer au client | *Integer* | | bytes_uploaded_int | Taille (en octets) de la requête envoyée par le client au Load Balancer | *Integer* | | time_duration_int | Durée (en millisecondes) de la session TCP au moment où la demande a été effectuée | *Integer* | @@ -184,7 +184,7 @@ Maintenant que vos logs sont ingérés et stockés dans votre flux de données L - Dans votre espace client, récupérez le nom d'utilisateur LDP (ex: logs-xxxx) et son mot de passe sur la page d'accueil de votre compte Logs Data Platform. Vous pouvez vous référer au [Guide de démarrage rapide pour Logs Data Platform](/pages/manage_and_operate/observability/logs_data_platform/getting_started_quick_start). - Ouvrir l'interface utilisateur Graylog. Vous pouvez récupérer le lien sur la page d'accueil de votre compte ou en utilisant votre point d'accès en fonction de la région de votre compte (par exemple : la région de Gravelines est `https://gra1.logs.ovh.com/`). - Connectez-vous à Graylog en utilisant votre nom d'utilisateur et votre mot de passe Logs Data Platform. -- Parcourez vos logs dans le flux de données de votre compte Logs Data Platform. Vous pouvez consulter la documentation [Graylog writing search queries (EN)](https://go2docs.graylog.org/current/making_sense_of_your_log_data/writing_search_queries.html){.external} pour plus de détails sur la syntaxe de recherche. +- Parcourez vos logs dans le flux de données de votre compte Logs Data Platform. Vous pouvez consulter la documentation [Graylog writing search queries (EN)](https://go2docs.graylog.org/current/making_sense_of_your_log_data/writing_search_queries.html) pour plus de détails sur la syntaxe de recherche. Reportez-vous à la documentation suivante : [Logs Data Platform - Visualizing, querying and exploiting your logs (EN)](/products/observability-logs-data-platform-visualizing-querying-exploiting) pour plus de détails sur l'utilisation de vos logs avec Logs Data Platform, y compris sur la façon de : diff --git a/pages/network/load_balancer/use_presentation/guide.de-de.md b/pages/network/load_balancer/use_presentation/guide.de-de.md index 7271ee217c2..744ce71274b 100644 --- a/pages/network/load_balancer/use_presentation/guide.de-de.md +++ b/pages/network/load_balancer/use_presentation/guide.de-de.md @@ -111,10 +111,10 @@ Sorgen Sie für gleichmäßige Verteilung und Redundanz Ihrer Datenbanken: ## Weiterführende Informationen -[Mehr zum Thema Lastverteilung](http://ovh.to/PhFmeK8){.external}. +[Mehr zum Thema Lastverteilung](http://ovh.to/PhFmeK8). -[Mehr zum Thema HAProxy](http://www.haproxy.org/#desc){.external}. +[Mehr zum Thema HAProxy](http://www.haproxy.org/#desc). -[Mehr zum Thema Nginx](https://de.wikipedia.org/wiki/Nginx){.external}. +[Mehr zum Thema Nginx](https://de.wikipedia.org/wiki/Nginx). Für den Austausch mit unserer User Community gehen Sie auf . \ No newline at end of file diff --git a/pages/network/load_balancer/use_presentation/guide.en-asia.md b/pages/network/load_balancer/use_presentation/guide.en-asia.md index c32478369ab..e15353f8b0e 100644 --- a/pages/network/load_balancer/use_presentation/guide.en-asia.md +++ b/pages/network/load_balancer/use_presentation/guide.en-asia.md @@ -110,10 +110,10 @@ Balance your databases, and make them redundant. ## Go further -[Find out more about load balancing](https://en.wikipedia.org/wiki/Load_balancing){.external}. +[Find out more about load balancing](https://en.wikipedia.org/wiki/Load_balancing). -[Find out more about HAProxy](http://www.haproxy.org/#desc){.external}. +[Find out more about HAProxy](http://www.haproxy.org/#desc). -[Find out more about Nginx](https://en.wikipedia.org/wiki/Nginx){.external}. +[Find out more about Nginx](https://en.wikipedia.org/wiki/Nginx). Join our community of users on . diff --git a/pages/network/load_balancer/use_presentation/guide.en-au.md b/pages/network/load_balancer/use_presentation/guide.en-au.md index c32478369ab..e15353f8b0e 100644 --- a/pages/network/load_balancer/use_presentation/guide.en-au.md +++ b/pages/network/load_balancer/use_presentation/guide.en-au.md @@ -110,10 +110,10 @@ Balance your databases, and make them redundant. ## Go further -[Find out more about load balancing](https://en.wikipedia.org/wiki/Load_balancing){.external}. +[Find out more about load balancing](https://en.wikipedia.org/wiki/Load_balancing). -[Find out more about HAProxy](http://www.haproxy.org/#desc){.external}. +[Find out more about HAProxy](http://www.haproxy.org/#desc). -[Find out more about Nginx](https://en.wikipedia.org/wiki/Nginx){.external}. +[Find out more about Nginx](https://en.wikipedia.org/wiki/Nginx). Join our community of users on . diff --git a/pages/network/load_balancer/use_presentation/guide.en-ca.md b/pages/network/load_balancer/use_presentation/guide.en-ca.md index c32478369ab..e15353f8b0e 100644 --- a/pages/network/load_balancer/use_presentation/guide.en-ca.md +++ b/pages/network/load_balancer/use_presentation/guide.en-ca.md @@ -110,10 +110,10 @@ Balance your databases, and make them redundant. ## Go further -[Find out more about load balancing](https://en.wikipedia.org/wiki/Load_balancing){.external}. +[Find out more about load balancing](https://en.wikipedia.org/wiki/Load_balancing). -[Find out more about HAProxy](http://www.haproxy.org/#desc){.external}. +[Find out more about HAProxy](http://www.haproxy.org/#desc). -[Find out more about Nginx](https://en.wikipedia.org/wiki/Nginx){.external}. +[Find out more about Nginx](https://en.wikipedia.org/wiki/Nginx). Join our community of users on . diff --git a/pages/network/load_balancer/use_presentation/guide.en-gb.md b/pages/network/load_balancer/use_presentation/guide.en-gb.md index ef828456e58..21397da777f 100644 --- a/pages/network/load_balancer/use_presentation/guide.en-gb.md +++ b/pages/network/load_balancer/use_presentation/guide.en-gb.md @@ -110,10 +110,10 @@ Balance your databases, and make them redundant. ## Go further -[Find out more about load balancing](https://en.wikipedia.org/wiki/Load_balancing){.external}. +[Find out more about load balancing](https://en.wikipedia.org/wiki/Load_balancing). -[Find out more about HAProxy](http://www.haproxy.org/#desc){.external}. +[Find out more about HAProxy](http://www.haproxy.org/#desc). -[Find out more about Nginx](https://en.wikipedia.org/wiki/Nginx){.external}. +[Find out more about Nginx](https://en.wikipedia.org/wiki/Nginx). Join our community of users on . \ No newline at end of file diff --git a/pages/network/load_balancer/use_presentation/guide.en-sg.md b/pages/network/load_balancer/use_presentation/guide.en-sg.md index c32478369ab..e15353f8b0e 100644 --- a/pages/network/load_balancer/use_presentation/guide.en-sg.md +++ b/pages/network/load_balancer/use_presentation/guide.en-sg.md @@ -110,10 +110,10 @@ Balance your databases, and make them redundant. ## Go further -[Find out more about load balancing](https://en.wikipedia.org/wiki/Load_balancing){.external}. +[Find out more about load balancing](https://en.wikipedia.org/wiki/Load_balancing). -[Find out more about HAProxy](http://www.haproxy.org/#desc){.external}. +[Find out more about HAProxy](http://www.haproxy.org/#desc). -[Find out more about Nginx](https://en.wikipedia.org/wiki/Nginx){.external}. +[Find out more about Nginx](https://en.wikipedia.org/wiki/Nginx). Join our community of users on . diff --git a/pages/network/load_balancer/use_presentation/guide.en-us.md b/pages/network/load_balancer/use_presentation/guide.en-us.md index c32478369ab..e15353f8b0e 100644 --- a/pages/network/load_balancer/use_presentation/guide.en-us.md +++ b/pages/network/load_balancer/use_presentation/guide.en-us.md @@ -110,10 +110,10 @@ Balance your databases, and make them redundant. ## Go further -[Find out more about load balancing](https://en.wikipedia.org/wiki/Load_balancing){.external}. +[Find out more about load balancing](https://en.wikipedia.org/wiki/Load_balancing). -[Find out more about HAProxy](http://www.haproxy.org/#desc){.external}. +[Find out more about HAProxy](http://www.haproxy.org/#desc). -[Find out more about Nginx](https://en.wikipedia.org/wiki/Nginx){.external}. +[Find out more about Nginx](https://en.wikipedia.org/wiki/Nginx). Join our community of users on . diff --git a/pages/network/load_balancer/use_presentation/guide.es-es.md b/pages/network/load_balancer/use_presentation/guide.es-es.md index 33c87dc5429..2426c3c5f6c 100644 --- a/pages/network/load_balancer/use_presentation/guide.es-es.md +++ b/pages/network/load_balancer/use_presentation/guide.es-es.md @@ -6,7 +6,7 @@ updated: 2018-01-17 ## Objetivo -El nuevo [Load Balancer de OVH](/links/network/load-balancer){.external} es un balanceador de carga (*load balancer*) que combina fiabilidad y una gran flexibilidad en la configuración. Usted solo tiene que configurar sus productos con el Load Balancer de OVH y nosotros nos encargamos del resto. +El nuevo [Load Balancer de OVH](/links/network/load-balancer) es un balanceador de carga (*load balancer*) que combina fiabilidad y una gran flexibilidad en la configuración. Usted solo tiene que configurar sus productos con el Load Balancer de OVH y nosotros nos encargamos del resto. **Esta guía explica brevemente el funcionamiento del nuevo Load Balancer de OVH.** @@ -19,7 +19,7 @@ El nuevo [Load Balancer de OVH](/links/network/load-balancer){.external} es un b Este nuevo producto está basado en tecnologías *open source* muy robustas: HAProxy para el tráfico TCP y Nginx para el tráfico UDP. -¡Se acabaron las limitaciones! El nuevo [Load Balancer de OVH](/links/network/load-balancer){.external} se puede utilizar con diferentes protocolos: +¡Se acabaron las limitaciones! El nuevo [Load Balancer de OVH](/links/network/load-balancer) se puede utilizar con diferentes protocolos: |Tipo|Descripción|Ventajas|Tecnología| |---|---|---|---| @@ -111,10 +111,10 @@ Equilibre y redunde sus bases de datos. ## Más información -[Más información sobre el balanceo de carga](https://es.wikipedia.org/wiki/Balanceador_de_carga){.external} +[Más información sobre el balanceo de carga](https://es.wikipedia.org/wiki/Balanceador_de_carga) -[Más información sobre HAProxy](http://www.haproxy.org/#desc){.external} +[Más información sobre HAProxy](http://www.haproxy.org/#desc) -[Más información sobre Nginx](https://es.wikipedia.org/wiki/Nginx){.external} +[Más información sobre Nginx](https://es.wikipedia.org/wiki/Nginx) Interactúe con nuestra comunidad de usuarios en . \ No newline at end of file diff --git a/pages/network/load_balancer/use_presentation/guide.es-us.md b/pages/network/load_balancer/use_presentation/guide.es-us.md index 78f73643a27..187a298c577 100644 --- a/pages/network/load_balancer/use_presentation/guide.es-us.md +++ b/pages/network/load_balancer/use_presentation/guide.es-us.md @@ -6,7 +6,7 @@ updated: 2018-01-17 ## Objetivo -El nuevo [Load Balancer de OVHcloud](https://www.ovh.com/world/es/soluciones/load-balancer/){.external} es un balanceador de carga (*load balancer*) que combina fiabilidad y una gran flexibilidad en la configuración. Usted solo tiene que configurar sus productos con el Load Balancer de OVHcloud y nosotros nos encargamos del resto. +El nuevo [Load Balancer de OVHcloud](https://www.ovh.com/world/es/soluciones/load-balancer/) es un balanceador de carga (*load balancer*) que combina fiabilidad y una gran flexibilidad en la configuración. Usted solo tiene que configurar sus productos con el Load Balancer de OVHcloud y nosotros nos encargamos del resto. **Esta guía explica brevemente el funcionamiento del nuevo Load Balancer de OVHcloud.** @@ -19,7 +19,7 @@ El nuevo [Load Balancer de OVHcloud](https://www.ovh.com/world/es/soluciones/loa Este nuevo producto está basado en tecnologías *open source* muy robustas: HAProxy para el tráfico TCP y Nginx para el tráfico UDP. -¡Se acabaron las limitaciones! El nuevo [Load Balancer de OVHcloud](https://www.ovh.com/world/es/soluciones/load-balancer/){.external} se puede utilizar con diferentes protocolos: +¡Se acabaron las limitaciones! El nuevo [Load Balancer de OVHcloud](https://www.ovh.com/world/es/soluciones/load-balancer/) se puede utilizar con diferentes protocolos: |Tipo|Descripción|Ventajas|Tecnología| |---|---|---|---| @@ -111,10 +111,10 @@ Equilibre y redunde sus bases de datos. ## Más información -[Más información sobre el balanceo de carga](https://es.wikipedia.org/wiki/Balanceador_de_carga){.external} +[Más información sobre el balanceo de carga](https://es.wikipedia.org/wiki/Balanceador_de_carga) -[Más información sobre HAProxy](http://www.haproxy.org/#desc){.external} +[Más información sobre HAProxy](http://www.haproxy.org/#desc) -[Más información sobre Nginx](https://es.wikipedia.org/wiki/Nginx){.external} +[Más información sobre Nginx](https://es.wikipedia.org/wiki/Nginx) Interactúe con nuestra comunidad de usuarios en . diff --git a/pages/network/load_balancer/use_presentation/guide.fr-ca.md b/pages/network/load_balancer/use_presentation/guide.fr-ca.md index 9c6d5ccc49f..926bee8a68c 100644 --- a/pages/network/load_balancer/use_presentation/guide.fr-ca.md +++ b/pages/network/load_balancer/use_presentation/guide.fr-ca.md @@ -6,7 +6,7 @@ updated: 2018-01-17 ## Objectif -La nouvelle offre [OVHcloud Load Balancer](https://www.ovh.com/ca/fr/solutions/load-balancer/){.external} est un répartiteur de charge (load balancer) qui allie souplesse de configuration et fiabilité. Vous n'avez qu'à configurer vos produits avec le Load Balancer OVHcloud et nous nous occupons du reste ! +La nouvelle offre [OVHcloud Load Balancer](https://www.ovh.com/ca/fr/solutions/load-balancer/) est un répartiteur de charge (load balancer) qui allie souplesse de configuration et fiabilité. Vous n'avez qu'à configurer vos produits avec le Load Balancer OVHcloud et nous nous occupons du reste ! **Découvrez vite la nouvelle offre OVHcloud Load Balancer.** @@ -19,7 +19,7 @@ La nouvelle offre [OVHcloud Load Balancer](https://www.ovh.com/ca/fr/solutions/l Cette nouvelle offre est basée sur de robustes solutions open source : Haproxy pour les flux TCP et Nginx pour les flux UDP. -Plus de limitations ! La nouvelle offre [OVHcloud Load Balancer](https://www.ovh.com/ca/fr/solutions/load-balancer/){.external} peut être utilisée pour fonctionner avec différents protocoles : +Plus de limitations ! La nouvelle offre [OVHcloud Load Balancer](https://www.ovh.com/ca/fr/solutions/load-balancer/) peut être utilisée pour fonctionner avec différents protocoles : |Type|Description|Avantages|Technologie| |---|---|---|---| @@ -111,10 +111,10 @@ Répartissez la charge entre vos serveurs de messagerie : ## Aller plus loin -[En apprendre plus sur la répartition de charge](https://fr.wikipedia.org/wiki/Repartition_de_charge){.external}. +[En apprendre plus sur la répartition de charge](https://fr.wikipedia.org/wiki/Repartition_de_charge). -[En apprendre plus sur Haproxy](http://www.haproxy.org/#desc){.external}. +[En apprendre plus sur Haproxy](http://www.haproxy.org/#desc). -[En apprendre plus sur Nginx](https://fr.wikipedia.org/wiki/Nginx){.external}. +[En apprendre plus sur Nginx](https://fr.wikipedia.org/wiki/Nginx). Échangez avec notre [communauté d'utilisateurs](/links/community). diff --git a/pages/network/load_balancer/use_presentation/guide.fr-fr.md b/pages/network/load_balancer/use_presentation/guide.fr-fr.md index de32a8c030e..f31ecdb2b5d 100644 --- a/pages/network/load_balancer/use_presentation/guide.fr-fr.md +++ b/pages/network/load_balancer/use_presentation/guide.fr-fr.md @@ -111,10 +111,10 @@ Répartissez la charge entre vos serveurs de messagerie : ## Aller plus loin -[En apprendre plus sur la répartition de charge](https://fr.wikipedia.org/wiki/Repartition_de_charge){.external}. +[En apprendre plus sur la répartition de charge](https://fr.wikipedia.org/wiki/Repartition_de_charge). -[En apprendre plus sur Haproxy](http://www.haproxy.org/#desc){.external}. +[En apprendre plus sur Haproxy](http://www.haproxy.org/#desc). -[En apprendre plus sur Nginx](https://fr.wikipedia.org/wiki/Nginx){.external}. +[En apprendre plus sur Nginx](https://fr.wikipedia.org/wiki/Nginx). Échangez avec notre [communauté d'utilisateurs](/links/community). diff --git a/pages/network/load_balancer/use_presentation/guide.it-it.md b/pages/network/load_balancer/use_presentation/guide.it-it.md index 93db203afdd..e522f22e7bd 100644 --- a/pages/network/load_balancer/use_presentation/guide.it-it.md +++ b/pages/network/load_balancer/use_presentation/guide.it-it.md @@ -6,7 +6,7 @@ updated: 2018-01-17 ## Obiettivo -Il nuovo [OVH Load Balancer](https://www.ovh.it/soluzioni/load-balancer/){.external} è un ripartitore di carico che combina flessibilità e affidabilità. Non dovrai fare altro che configurare i tuoi prodotti con OVH Load Balancer e noi ci occuperemo di tutto il resto! +Il nuovo [OVH Load Balancer](https://www.ovh.it/soluzioni/load-balancer/) è un ripartitore di carico che combina flessibilità e affidabilità. Non dovrai fare altro che configurare i tuoi prodotti con OVH Load Balancer e noi ci occuperemo di tutto il resto! **Scopri subito il nuovo OVH Load Balancer** @@ -19,7 +19,7 @@ Il nuovo [OVH Load Balancer](https://www.ovh.it/soluzioni/load-balancer/){.exter Questo servizio si basa su tecnologie open source: HAProxy per il traffico TCP e Nginx per il traffico UDP. -Senza restrizioni! La nuova soluzione di [OVH Load Balancer](https://www.ovh.it/soluzioni/load-balancer/){.external} è stata ideata per funzionare con diversi protocolli: +Senza restrizioni! La nuova soluzione di [OVH Load Balancer](https://www.ovh.it/soluzioni/load-balancer/) è stata ideata per funzionare con diversi protocolli: |Tipo|Descrizione|Vantaggi|Tecnologia| |---|---|---|---| @@ -111,10 +111,10 @@ Distribuzione e ridondanza dei tuoi database. ## Per saperne di più -[Load balancing](https://it.wikipedia.org/wiki/Load_balancing){.external}. +[Load balancing](https://it.wikipedia.org/wiki/Load_balancing). -[Haproxy](https://en.wikipedia.org/wiki/HAProxy){.external}. +[Haproxy](https://en.wikipedia.org/wiki/HAProxy). -[Nginx](https://it.wikipedia.org/wiki/Nginx){.external}. +[Nginx](https://it.wikipedia.org/wiki/Nginx). Contatta la nostra Community di utenti all’indirizzo . \ No newline at end of file diff --git a/pages/network/load_balancer/use_presentation/guide.pl-pl.md b/pages/network/load_balancer/use_presentation/guide.pl-pl.md index bffa6a493c3..52a34931d74 100644 --- a/pages/network/load_balancer/use_presentation/guide.pl-pl.md +++ b/pages/network/load_balancer/use_presentation/guide.pl-pl.md @@ -109,8 +109,8 @@ Dzięki Load balancerowi, zadbasz o redundancję i zrównoważone obciążenie s ## Sprawdź również -[Dowiedz się więcej o Haproxy](http://www.haproxy.org/#desc){.external}. +[Dowiedz się więcej o Haproxy](http://www.haproxy.org/#desc). -[Dowiedz się więcej o Nginx](https://pl.wikipedia.org/wiki/Nginx){.external}. +[Dowiedz się więcej o Nginx](https://pl.wikipedia.org/wiki/Nginx). Przyłącz się do społeczności naszych użytkowników na stronie. \ No newline at end of file diff --git a/pages/network/load_balancer/use_presentation/guide.pt-pt.md b/pages/network/load_balancer/use_presentation/guide.pt-pt.md index a0e086e58d1..7c78349e3a5 100644 --- a/pages/network/load_balancer/use_presentation/guide.pt-pt.md +++ b/pages/network/load_balancer/use_presentation/guide.pt-pt.md @@ -111,10 +111,10 @@ Equilibre o esforço das base de dados e crie redundâncias: ## Quer saber mais? Consulte a informação abaixo -[Saber mais sobre o Load Balancer](https://pt.wikipedia.org/wiki/Balanceamento_de_carga){.external}. +[Saber mais sobre o Load Balancer](https://pt.wikipedia.org/wiki/Balanceamento_de_carga). -[Saber mais sobre Haproxy](http://www.haproxy.org/#desc){.external}. +[Saber mais sobre Haproxy](http://www.haproxy.org/#desc). -[Saber mais sobre Nginx](https://pt.wikipedia.org/wiki/Nginx){.external}. +[Saber mais sobre Nginx](https://pt.wikipedia.org/wiki/Nginx). Ou fale com a nossa comunidade de utilizadores: . \ No newline at end of file diff --git a/pages/network/load_balancer/vrack_and_loadbalancer/guide.fr-fr.md b/pages/network/load_balancer/vrack_and_loadbalancer/guide.fr-fr.md index 9eaefa0620b..ef88dd45ff1 100644 --- a/pages/network/load_balancer/vrack_and_loadbalancer/guide.fr-fr.md +++ b/pages/network/load_balancer/vrack_and_loadbalancer/guide.fr-fr.md @@ -16,7 +16,7 @@ Avant de vous lancer, si vous ne l’avez pas encore lue, nous vous conseillons - Posséder une offre [OVHcloud Load balancer](/links/network/load-balancer) dans votre compte OVHcloud. - Être connecté à votre [espace client OVHcloud](/links/manager). -- Être connecté à l'[API OVHcloud](/links/api){.external}. +- Être connecté à l'[API OVHcloud](/links/api). - Posséder une ferme configurée - Posséder un frontend configuré diff --git a/pages/network/ovhcloud_connect/occ-howto-api/guide.de-de.md b/pages/network/ovhcloud_connect/occ-howto-api/guide.de-de.md index a9ad6c19ef3..a9207b2a78b 100644 --- a/pages/network/ovhcloud_connect/occ-howto-api/guide.de-de.md +++ b/pages/network/ovhcloud_connect/occ-howto-api/guide.de-de.md @@ -17,7 +17,7 @@ Configuring the OVHcloud Connect solution can be done via API. > - an [OVHcloud Connect service](/links/network/ovhcloud-connect) -- access to the [OVHcloud APIv6](/links/api){.external} (create your credentials by consulting [this guide](/pages/manage_and_operate/api/first-steps)) +- access to the [OVHcloud APIv6](/links/api) (create your credentials by consulting [this guide](/pages/manage_and_operate/api/first-steps)) ## Instructions diff --git a/pages/network/ovhcloud_connect/occ-howto-api/guide.en-asia.md b/pages/network/ovhcloud_connect/occ-howto-api/guide.en-asia.md index a9ad6c19ef3..a9207b2a78b 100644 --- a/pages/network/ovhcloud_connect/occ-howto-api/guide.en-asia.md +++ b/pages/network/ovhcloud_connect/occ-howto-api/guide.en-asia.md @@ -17,7 +17,7 @@ Configuring the OVHcloud Connect solution can be done via API. > - an [OVHcloud Connect service](/links/network/ovhcloud-connect) -- access to the [OVHcloud APIv6](/links/api){.external} (create your credentials by consulting [this guide](/pages/manage_and_operate/api/first-steps)) +- access to the [OVHcloud APIv6](/links/api) (create your credentials by consulting [this guide](/pages/manage_and_operate/api/first-steps)) ## Instructions diff --git a/pages/network/ovhcloud_connect/occ-howto-api/guide.en-au.md b/pages/network/ovhcloud_connect/occ-howto-api/guide.en-au.md index a9ad6c19ef3..a9207b2a78b 100644 --- a/pages/network/ovhcloud_connect/occ-howto-api/guide.en-au.md +++ b/pages/network/ovhcloud_connect/occ-howto-api/guide.en-au.md @@ -17,7 +17,7 @@ Configuring the OVHcloud Connect solution can be done via API. > - an [OVHcloud Connect service](/links/network/ovhcloud-connect) -- access to the [OVHcloud APIv6](/links/api){.external} (create your credentials by consulting [this guide](/pages/manage_and_operate/api/first-steps)) +- access to the [OVHcloud APIv6](/links/api) (create your credentials by consulting [this guide](/pages/manage_and_operate/api/first-steps)) ## Instructions diff --git a/pages/network/ovhcloud_connect/occ-howto-api/guide.en-ca.md b/pages/network/ovhcloud_connect/occ-howto-api/guide.en-ca.md index a9ad6c19ef3..a9207b2a78b 100644 --- a/pages/network/ovhcloud_connect/occ-howto-api/guide.en-ca.md +++ b/pages/network/ovhcloud_connect/occ-howto-api/guide.en-ca.md @@ -17,7 +17,7 @@ Configuring the OVHcloud Connect solution can be done via API. > - an [OVHcloud Connect service](/links/network/ovhcloud-connect) -- access to the [OVHcloud APIv6](/links/api){.external} (create your credentials by consulting [this guide](/pages/manage_and_operate/api/first-steps)) +- access to the [OVHcloud APIv6](/links/api) (create your credentials by consulting [this guide](/pages/manage_and_operate/api/first-steps)) ## Instructions diff --git a/pages/network/ovhcloud_connect/occ-howto-api/guide.en-gb.md b/pages/network/ovhcloud_connect/occ-howto-api/guide.en-gb.md index a9ad6c19ef3..a9207b2a78b 100644 --- a/pages/network/ovhcloud_connect/occ-howto-api/guide.en-gb.md +++ b/pages/network/ovhcloud_connect/occ-howto-api/guide.en-gb.md @@ -17,7 +17,7 @@ Configuring the OVHcloud Connect solution can be done via API. > - an [OVHcloud Connect service](/links/network/ovhcloud-connect) -- access to the [OVHcloud APIv6](/links/api){.external} (create your credentials by consulting [this guide](/pages/manage_and_operate/api/first-steps)) +- access to the [OVHcloud APIv6](/links/api) (create your credentials by consulting [this guide](/pages/manage_and_operate/api/first-steps)) ## Instructions diff --git a/pages/network/ovhcloud_connect/occ-howto-api/guide.en-ie.md b/pages/network/ovhcloud_connect/occ-howto-api/guide.en-ie.md index a9ad6c19ef3..a9207b2a78b 100644 --- a/pages/network/ovhcloud_connect/occ-howto-api/guide.en-ie.md +++ b/pages/network/ovhcloud_connect/occ-howto-api/guide.en-ie.md @@ -17,7 +17,7 @@ Configuring the OVHcloud Connect solution can be done via API. > - an [OVHcloud Connect service](/links/network/ovhcloud-connect) -- access to the [OVHcloud APIv6](/links/api){.external} (create your credentials by consulting [this guide](/pages/manage_and_operate/api/first-steps)) +- access to the [OVHcloud APIv6](/links/api) (create your credentials by consulting [this guide](/pages/manage_and_operate/api/first-steps)) ## Instructions diff --git a/pages/network/ovhcloud_connect/occ-howto-api/guide.en-sg.md b/pages/network/ovhcloud_connect/occ-howto-api/guide.en-sg.md index a9ad6c19ef3..a9207b2a78b 100644 --- a/pages/network/ovhcloud_connect/occ-howto-api/guide.en-sg.md +++ b/pages/network/ovhcloud_connect/occ-howto-api/guide.en-sg.md @@ -17,7 +17,7 @@ Configuring the OVHcloud Connect solution can be done via API. > - an [OVHcloud Connect service](/links/network/ovhcloud-connect) -- access to the [OVHcloud APIv6](/links/api){.external} (create your credentials by consulting [this guide](/pages/manage_and_operate/api/first-steps)) +- access to the [OVHcloud APIv6](/links/api) (create your credentials by consulting [this guide](/pages/manage_and_operate/api/first-steps)) ## Instructions diff --git a/pages/network/ovhcloud_connect/occ-howto-api/guide.en-us.md b/pages/network/ovhcloud_connect/occ-howto-api/guide.en-us.md index a9ad6c19ef3..a9207b2a78b 100644 --- a/pages/network/ovhcloud_connect/occ-howto-api/guide.en-us.md +++ b/pages/network/ovhcloud_connect/occ-howto-api/guide.en-us.md @@ -17,7 +17,7 @@ Configuring the OVHcloud Connect solution can be done via API. > - an [OVHcloud Connect service](/links/network/ovhcloud-connect) -- access to the [OVHcloud APIv6](/links/api){.external} (create your credentials by consulting [this guide](/pages/manage_and_operate/api/first-steps)) +- access to the [OVHcloud APIv6](/links/api) (create your credentials by consulting [this guide](/pages/manage_and_operate/api/first-steps)) ## Instructions diff --git a/pages/network/ovhcloud_connect/occ-howto-api/guide.es-es.md b/pages/network/ovhcloud_connect/occ-howto-api/guide.es-es.md index a9ad6c19ef3..a9207b2a78b 100644 --- a/pages/network/ovhcloud_connect/occ-howto-api/guide.es-es.md +++ b/pages/network/ovhcloud_connect/occ-howto-api/guide.es-es.md @@ -17,7 +17,7 @@ Configuring the OVHcloud Connect solution can be done via API. > - an [OVHcloud Connect service](/links/network/ovhcloud-connect) -- access to the [OVHcloud APIv6](/links/api){.external} (create your credentials by consulting [this guide](/pages/manage_and_operate/api/first-steps)) +- access to the [OVHcloud APIv6](/links/api) (create your credentials by consulting [this guide](/pages/manage_and_operate/api/first-steps)) ## Instructions diff --git a/pages/network/ovhcloud_connect/occ-howto-api/guide.es-us.md b/pages/network/ovhcloud_connect/occ-howto-api/guide.es-us.md index a9ad6c19ef3..a9207b2a78b 100644 --- a/pages/network/ovhcloud_connect/occ-howto-api/guide.es-us.md +++ b/pages/network/ovhcloud_connect/occ-howto-api/guide.es-us.md @@ -17,7 +17,7 @@ Configuring the OVHcloud Connect solution can be done via API. > - an [OVHcloud Connect service](/links/network/ovhcloud-connect) -- access to the [OVHcloud APIv6](/links/api){.external} (create your credentials by consulting [this guide](/pages/manage_and_operate/api/first-steps)) +- access to the [OVHcloud APIv6](/links/api) (create your credentials by consulting [this guide](/pages/manage_and_operate/api/first-steps)) ## Instructions diff --git a/pages/network/ovhcloud_connect/occ-howto-api/guide.fr-ca.md b/pages/network/ovhcloud_connect/occ-howto-api/guide.fr-ca.md index 0b00f163e29..e53222d8c0a 100644 --- a/pages/network/ovhcloud_connect/occ-howto-api/guide.fr-ca.md +++ b/pages/network/ovhcloud_connect/occ-howto-api/guide.fr-ca.md @@ -17,7 +17,7 @@ La mise en place de l'offre OVHcloud Connect peut se faire directement depuis le > * Posséder une offre [OVHcloud Connect](/links/network/ovhcloud-connect) dans votre compte OVHcloud. -* Être connecté aux [API OVHcloud](/links/api){.external}. +* Être connecté aux [API OVHcloud](/links/api). * Avoir [créé vos credentials pour l'utilisation des API OVHcloud](/pages/manage_and_operate/api/first-steps). ## En pratique diff --git a/pages/network/ovhcloud_connect/occ-howto-api/guide.fr-fr.md b/pages/network/ovhcloud_connect/occ-howto-api/guide.fr-fr.md index 0b00f163e29..e53222d8c0a 100644 --- a/pages/network/ovhcloud_connect/occ-howto-api/guide.fr-fr.md +++ b/pages/network/ovhcloud_connect/occ-howto-api/guide.fr-fr.md @@ -17,7 +17,7 @@ La mise en place de l'offre OVHcloud Connect peut se faire directement depuis le > * Posséder une offre [OVHcloud Connect](/links/network/ovhcloud-connect) dans votre compte OVHcloud. -* Être connecté aux [API OVHcloud](/links/api){.external}. +* Être connecté aux [API OVHcloud](/links/api). * Avoir [créé vos credentials pour l'utilisation des API OVHcloud](/pages/manage_and_operate/api/first-steps). ## En pratique diff --git a/pages/network/ovhcloud_connect/occ-howto-api/guide.it-it.md b/pages/network/ovhcloud_connect/occ-howto-api/guide.it-it.md index a9ad6c19ef3..a9207b2a78b 100644 --- a/pages/network/ovhcloud_connect/occ-howto-api/guide.it-it.md +++ b/pages/network/ovhcloud_connect/occ-howto-api/guide.it-it.md @@ -17,7 +17,7 @@ Configuring the OVHcloud Connect solution can be done via API. > - an [OVHcloud Connect service](/links/network/ovhcloud-connect) -- access to the [OVHcloud APIv6](/links/api){.external} (create your credentials by consulting [this guide](/pages/manage_and_operate/api/first-steps)) +- access to the [OVHcloud APIv6](/links/api) (create your credentials by consulting [this guide](/pages/manage_and_operate/api/first-steps)) ## Instructions diff --git a/pages/network/ovhcloud_connect/occ-howto-api/guide.pl-pl.md b/pages/network/ovhcloud_connect/occ-howto-api/guide.pl-pl.md index a9ad6c19ef3..a9207b2a78b 100644 --- a/pages/network/ovhcloud_connect/occ-howto-api/guide.pl-pl.md +++ b/pages/network/ovhcloud_connect/occ-howto-api/guide.pl-pl.md @@ -17,7 +17,7 @@ Configuring the OVHcloud Connect solution can be done via API. > - an [OVHcloud Connect service](/links/network/ovhcloud-connect) -- access to the [OVHcloud APIv6](/links/api){.external} (create your credentials by consulting [this guide](/pages/manage_and_operate/api/first-steps)) +- access to the [OVHcloud APIv6](/links/api) (create your credentials by consulting [this guide](/pages/manage_and_operate/api/first-steps)) ## Instructions diff --git a/pages/network/ovhcloud_connect/occ-howto-api/guide.pt-pt.md b/pages/network/ovhcloud_connect/occ-howto-api/guide.pt-pt.md index a9ad6c19ef3..a9207b2a78b 100644 --- a/pages/network/ovhcloud_connect/occ-howto-api/guide.pt-pt.md +++ b/pages/network/ovhcloud_connect/occ-howto-api/guide.pt-pt.md @@ -17,7 +17,7 @@ Configuring the OVHcloud Connect solution can be done via API. > - an [OVHcloud Connect service](/links/network/ovhcloud-connect) -- access to the [OVHcloud APIv6](/links/api){.external} (create your credentials by consulting [this guide](/pages/manage_and_operate/api/first-steps)) +- access to the [OVHcloud APIv6](/links/api) (create your credentials by consulting [this guide](/pages/manage_and_operate/api/first-steps)) ## Instructions