- Sort Score
- Num 10 results
- Language All
Results 11 - 20 of 272 for IP (0.02 seconds)
-
.github/workflows/mint/nginx-8-node.conf
proxy_set_header Host $http_host; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Forwarded-Proto $scheme; proxy_set_header X-NginX-Proxy true; # This is necessary to pass the correct IP to be hashed real_ip_header X-Real-IP; proxy_connect_timeout 300;Created: Sun Dec 28 19:28:13 GMT 2025 - Last Modified: Wed May 15 16:52:29 GMT 2024 - 3.4K bytes - Click Count (0) -
docs/es/docs/deployment/https.md
/// ### DNS { #dns } Ahora centrémonos en todas las partes realmente de HTTPS. Primero, el navegador consultaría con los **servidores DNS** cuál es la **IP del dominio**, en este caso, `someapp.example.com`.Created: Sun Dec 28 07:19:09 GMT 2025 - Last Modified: Tue Dec 16 16:33:45 GMT 2025 - 15.4K bytes - Click Count (0) -
docs/pt/docs/deployment/https.md
/// ### DNS { #dns } Agora vamos focar em todas as partes que realmente fazem parte do HTTPS. Primeiro, o navegador iria verificar com os servidores DNS qual o IP do domínio, nesse caso, `someapp.example.com`.Created: Sun Dec 28 07:19:09 GMT 2025 - Last Modified: Wed Nov 12 16:23:57 GMT 2025 - 14.8K bytes - Click Count (0) -
internal/config/dns/etcd_dns.go
t := time.Now().UTC() for ip := range c.domainIPs { bucketMsg, err := newCoreDNSMsg(ip, c.domainPort, defaultTTL, t) if err != nil { return err } for _, domainName := range c.domainNames { key := msgPath(fmt.Sprintf("%s.%s", bucket, domainName), c.prefixPath) key = key + etcdPathSeparator + ip ctx, cancel := context.WithTimeout(context.Background(), defaultContextTimeout)
Created: Sun Dec 28 19:28:13 GMT 2025 - Last Modified: Tue Feb 18 16:25:55 GMT 2025 - 8K bytes - Click Count (0) -
okhttp/src/commonJvmAndroid/kotlin/okhttp3/Dns.kt
import okhttp3.Dns.Companion.SYSTEM /** * A domain name service that resolves IP addresses for host names. Most applications will use the * [system DNS service][SYSTEM], which is the default. Some applications may provide their own * implementation to use a different DNS server, to prefer IPv6 addresses, to prefer IPv4 addresses, * or to force a specific known IP address. * * Implementations of this interface must be safe for concurrent use. */
Created: Fri Dec 26 11:42:13 GMT 2025 - Last Modified: Fri Dec 27 13:39:56 GMT 2024 - 2.2K bytes - Click Count (0) -
helm/minio/templates/NOTES.txt
MinIO can be accessed via port {{ .Values.service.port }} on an external IP address. Get the service external IP address by: kubectl get svc --namespace {{ .Release.Namespace }} -l app={{ template "minio.fullname" . }} Note that the public IP may take a couple of minutes to be available. You can now access MinIO server on http://<External-IP>:9000. Follow the below steps to connect to MinIO server with mc client:Created: Sun Dec 28 19:28:13 GMT 2025 - Last Modified: Tue Aug 12 18:20:36 GMT 2025 - 2.7K bytes - Click Count (0) -
.github/workflows/mint/nginx-1-node.conf
proxy_set_header Host $http_host; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Forwarded-Proto $scheme; proxy_set_header X-NginX-Proxy true; # This is necessary to pass the correct IP to be hashed real_ip_header X-Real-IP; proxy_connect_timeout 300;Created: Sun Dec 28 19:28:13 GMT 2025 - Last Modified: Fri Mar 31 21:38:10 GMT 2023 - 2.8K bytes - Click Count (1) -
docs/orchestration/docker-compose/nginx.conf
proxy_set_header Host $http_host; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Forwarded-Proto $scheme; proxy_set_header X-NginX-Proxy true; # This is necessary to pass the correct IP to be hashed real_ip_header X-Real-IP; proxy_connect_timeout 300;Created: Sun Dec 28 19:28:13 GMT 2025 - Last Modified: Sat Mar 05 06:32:39 GMT 2022 - 3K bytes - Click Count (0) -
docs/resiliency/nginx.conf
proxy_set_header Host $http_host; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Forwarded-Proto $scheme; proxy_set_header X-NginX-Proxy true; # This is necessary to pass the correct IP to be hashed real_ip_header X-Real-IP; proxy_connect_timeout 300;Created: Sun Dec 28 19:28:13 GMT 2025 - Last Modified: Sat Dec 21 04:24:45 GMT 2024 - 3K bytes - Click Count (0) -
docs/de/docs/deployment/https.md
/// ### DNS { #dns } Konzentrieren wir uns nun auf alle tatsächlichen HTTPS-Aspekte. Zuerst würde der Browser mithilfe der **DNS-Server** herausfinden, welches die **IP für die Domain** ist, in diesem Fall `someapp.example.com`.Created: Sun Dec 28 07:19:09 GMT 2025 - Last Modified: Sat Sep 20 15:10:09 GMT 2025 - 16.1K bytes - Click Count (0)