Search Options

Results per page
Sort
Preferred Languages
Advance

Results 1 - 10 of 12 for 443 (0.05 sec)

  1. okhttp/src/jvmTest/resources/web-platform-test-urltestdata.txt

    httpa://foo:80/  s:httpa p://foo:80/
    http://foo:-80/
    https://foo:443/  s:https h:foo p:/
    https://foo:80/  s:https h:foo port:80 p:/
    ftp://foo:21/  s:ftp h:foo p:/
    ftp://foo:80/  s:ftp h:foo port:80 p:/
    gopher://foo:70/  s:gopher h:foo p:/
    gopher://foo:443/  s:gopher h:foo port:443 p:/
    ws://foo:80/  s:ws h:foo p:/
    ws://foo:81/  s:ws h:foo port:81 p:/
    ws://foo:443/  s:ws h:foo port:443 p:/
    ws://foo:815/  s:ws h:foo port:815 p:/
    Registered: Fri Dec 26 11:42:13 UTC 2025
    - Last Modified: Fri Dec 27 13:39:56 UTC 2024
    - 14.3K bytes
    - Viewed (0)
  2. docs/en/docs/deployment/https.md

    <img src="/img/deployment/https/https01.drawio.svg">
    
    ### TLS Handshake Start { #tls-handshake-start }
    
    The browser would then communicate with that IP address on **port 443** (the HTTPS port).
    
    The first part of the communication is just to establish the connection between the client and the server and to decide the cryptographic keys they will use, etc.
    
    Registered: Sun Dec 28 07:19:09 UTC 2025
    - Last Modified: Sun Aug 31 19:34:08 UTC 2025
    - 14.3K bytes
    - Viewed (0)
  3. docs/pt/docs/deployment/https.md

    <img src="/img/deployment/https/https01.drawio.svg">
    
    ### Início do Handshake TLS { #tls-handshake-start }
    
    O navegador então irá comunicar-se com esse endereço IP na porta 443 (a porta HTTPS).
    
    A primeira parte dessa comunicação é apenas para estabelecer a conexão entre o cliente e o servidor e para decidir as chaves criptográficas a serem utilizadas, etc.
    
    Registered: Sun Dec 28 07:19:09 UTC 2025
    - Last Modified: Wed Nov 12 16:23:57 UTC 2025
    - 14.8K bytes
    - Viewed (0)
  4. docs/ru/docs/deployment/https.md

    <img src="/img/deployment/https/https01.drawio.svg">
    
    ### Начало TLS-рукопожатия { #tls-handshake-start }
    
    Далее браузер будет общаться с этим IP‑адресом на **порту 443** (порт HTTPS).
    
    Первая часть взаимодействия — установить соединение между клиентом и сервером и договориться о криптографических ключах и т.п.
    
    <img src="/img/deployment/https/https02.drawio.svg">
    
    Registered: Sun Dec 28 07:19:09 UTC 2025
    - Last Modified: Tue Sep 30 11:24:39 UTC 2025
    - 23K bytes
    - Viewed (0)
  5. docs/de/docs/deployment/https.md

    <img src="/img/deployment/https/https01.drawio.svg">
    
    ### TLS-Handshake-Start { #tls-handshake-start }
    
    Der Browser kommuniziert dann mit dieser IP-Adresse über **Port 443** (den HTTPS-Port).
    
    Der erste Teil der Kommunikation besteht lediglich darin, die Verbindung zwischen dem Client und dem Server herzustellen und die zu verwendenden kryptografischen Schlüssel usw. zu vereinbaren.
    
    Registered: Sun Dec 28 07:19:09 UTC 2025
    - Last Modified: Sat Sep 20 15:10:09 UTC 2025
    - 16.1K bytes
    - Viewed (0)
  6. cmd/endpoint_test.go

    		// Erasure Single Drive
    		{"localhost:9000", []string{"http://localhost/d1"}, "", Endpoints{}, -1, fmt.Errorf("use path style endpoint for SD setup")},
    		{":443", []string{"/d1"}, ":443", Endpoints{Endpoint{URL: &url.URL{Path: mustAbs("/d1")}, IsLocal: true}}, ErasureSDSetupType, nil},
    Registered: Sun Dec 28 19:28:13 UTC 2025
    - Last Modified: Fri Aug 29 02:39:48 UTC 2025
    - 18.9K bytes
    - Viewed (0)
  7. docs/zh/docs/deployment/https.md

    ### TLS 握手开始
    
    然后,浏览器将在**端口 443**(HTTPS 端口)上与该 IP 地址进行通信。
    
    通信的第一部分只是建立客户端和服务器之间的连接并决定它们将使用的加密密钥等。
    
    <img src="/img/deployment/https/https02.drawio.svg">
    
    客户端和服务器之间建立 TLS 连接的过程称为 **TLS 握手**。
    
    ### 带有 SNI 扩展的 TLS
    
    **服务器中只有一个进程**可以侦听特定 **IP 地址**的特定 **端口**。 可能有其他进程在同一 IP 地址的其他端口上侦听,但每个 IP 地址和端口组合只有一个进程。
    
    TLS (HTTPS) 默认使用端口`443`。 这就是我们需要的端口。
    
    由于只有一个进程可以监听此端口,因此监听端口的进程将是 **TLS 终止代理**。
    
    Registered: Sun Dec 28 07:19:09 UTC 2025
    - Last Modified: Sun May 11 13:37:26 UTC 2025
    - 10.7K bytes
    - Viewed (0)
  8. docs/es/docs/deployment/https.md

    <img src="/img/deployment/https/https01.drawio.svg">
    
    ### Inicio del Handshake TLS { #tls-handshake-start }
    
    El navegador luego se comunicaría con esa dirección IP en el **puerto 443** (el puerto HTTPS).
    
    La primera parte de la comunicación es solo para establecer la conexión entre el cliente y el servidor y decidir las claves criptográficas que usarán, etc.
    
    <img src="/img/deployment/https/https02.drawio.svg">
    Registered: Sun Dec 28 07:19:09 UTC 2025
    - Last Modified: Tue Dec 16 16:33:45 UTC 2025
    - 15.4K bytes
    - Viewed (0)
  9. docs/ja/docs/deployment/https.md

    DNSサーバーは、ブラウザに特定の**IPアドレス**を使用するように指示します。このIPアドレスは、DNSサーバーで設定した、あなたのサーバーが使用するパブリックIPアドレスになります。
    
    <img src="/img/deployment/https/https01.drawio.svg">
    
    ### TLS Handshake の開始
    
    ブラウザはIPアドレスと**ポート443**(HTTPSポート)で通信します。
    
    通信の最初の部分は、クライアントとサーバー間の接続を確立し、使用する暗号鍵などを決めるだけです。
    
    <img src="/img/deployment/https/https02.drawio.svg">
    
    TLS接続を確立するためのクライアントとサーバー間のこのやりとりは、**TLSハンドシェイク**と呼ばれます。
    
    ### SNI拡張機能付きのTLS
    
    Registered: Sun Dec 28 07:19:09 UTC 2025
    - Last Modified: Sun May 11 13:37:26 UTC 2025
    - 15.5K bytes
    - Viewed (0)
  10. helm/minio/values.yaml

        enabled: false
        ## @param networkPolicy.egress.ports Add individual ports to be allowed by the egress
        ## Add ports to the egress by specifying - port: <port number>
        ## E.X.
        ## - port: 80
        ## - port: 443
        ## - port: 53
        ##   protocol: UDP
        ##
        ports: []
        ## @param networkPolicy.egress.to Allow egress traffic to specific destinations
        ## Add destinations to the egress by specifying - ipBlock: <CIDR>
    Registered: Sun Dec 28 19:28:13 UTC 2025
    - Last Modified: Tue Aug 12 18:20:36 UTC 2025
    - 19.7K bytes
    - Viewed (1)
Back to top