Search Options

Results per page
Sort
Preferred Languages
Advance

Results 1 - 3 of 3 for Ports (0.07 sec)

  1. docs/en/docs/tutorial/cors.md

    So, all these are different origins:
    
    * `http://localhost`
    * `https://localhost`
    * `http://localhost:8080`
    
    Even if they are all in `localhost`, they use different protocols or ports, so, they are different "origins".
    
    ## Steps { #steps }
    
    Registered: Sun Sep 07 07:19:17 UTC 2025
    - Last Modified: Sun Aug 31 09:15:41 UTC 2025
    - 5.5K bytes
    - Viewed (0)
  2. docs/en/docs/deployment/concepts.md

    When you run **multiple processes** of the same API program, they are commonly called **workers**.
    
    ### Worker Processes and Ports { #worker-processes-and-ports }
    
    Remember from the docs [About HTTPS](https.md){.internal-link target=_blank} that only one process can be listening on one combination of port and IP address in a server?
    
    This is still true.
    
    Registered: Sun Sep 07 07:19:17 UTC 2025
    - Last Modified: Sun Aug 31 09:15:41 UTC 2025
    - 18.6K bytes
    - Viewed (0)
  3. docs/en/docs/deployment/https.md

    ### TLS with SNI Extension { #tls-with-sni-extension }
    
    **Only one process** in the server can be listening on a specific **port** in a specific **IP address**. There could be other processes listening on other ports in the same IP address, but only one for each combination of IP address and port.
    
    TLS (HTTPS) uses the specific port `443` by default. So that's the port we would need.
    
    Registered: Sun Sep 07 07:19:17 UTC 2025
    - Last Modified: Sun Aug 31 19:34:08 UTC 2025
    - 14.3K bytes
    - Viewed (0)
Back to top