}

  public void testToString() {
    // With ports.
    assertEquals("foo:101", "" + HostAndPort.fromString("foo:101"));
    assertEquals(":102", HostAndPort.fromString(":102").toString());
    assertEquals("[1::2]:103", HostAndPort.fromParts("1::2", 103).toString());
    assertEquals("[::1]:104", HostAndPort.fromString("[::1]:104").toString());

    // Without ports.
    assertEquals("foo", "" + HostAndPort.fromString("foo"));

  }

  public void testToString() {
    // With ports.
    assertEquals("foo:101", "" + HostAndPort.fromString("foo:101"));
    assertEquals(":102", HostAndPort.fromString(":102").toString());
    assertEquals("[1::2]:103", HostAndPort.fromParts("1::2", 103).toString());
    assertEquals("[::1]:104", HostAndPort.fromString("[::1]:104").toString());

    // Without ports.
    assertEquals("foo", "" + HostAndPort.fromString("foo"));

        }
    }

    @Nested
    @DisplayName("HTTP vs HTTPS Comparison Tests")
    class ProtocolComparisonTests {

        @Test
        @DisplayName("Should use different ports for HTTP and HTTPS")
        void testDifferentPorts() {
            // Given
            Handler httpsHandler = new Handler(null);

            // When
            int httpsPort = httpsHandler.getDefaultPort();

        }
    }

    @Nested
    @DisplayName("HTTP vs HTTPS Comparison Tests")
    class ProtocolComparisonTests {

        @Test
        @DisplayName("Should use different ports for HTTP and HTTPS")
        void testDifferentPorts() {
            // Given
            Handler httpsHandler = new Handler();

            // When
            int httpsPort = httpsHandler.getDefaultPort();

 * and initialization, including SSL setup, context path handling, and resource management.
 *
 * <p>The class handles system property configuration for paths, ports, and other
 * Fess-specific settings during application startup.</p>
 *
 * @since 1.0
 */
public class FessBoot extends TomcatBoot {

    /** Configuration file name for logging properties */

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 }

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.

### 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.

### TLS mit SNI-Erweiterung

**Nur ein Prozess** im Server kann an einem bestimmten **Port** einer bestimmten **IP-Adresse** lauschen. Möglicherweise gibt es andere Prozesse, die an anderen Ports dieselbe IP-Adresse abhören, jedoch nur einen für jede Kombination aus IP-Adresse und Port.

TLS (HTTPS) verwendet standardmäßig den spezifischen Port `443`. Das ist also der Port, den wir brauchen.

Wenn Sie mit **mehreren Prozessen** dasselbe API-Programm ausführen, werden diese üblicherweise als **<abbr title="Arbeiter">Worker</abbr>** bezeichnet.

### Workerprozesse und Ports

Erinnern Sie sich aus der Dokumentation [Über HTTPS](https.md){.internal-link target=_blank}, dass nur ein Prozess auf einer Kombination aus Port und IP-Adresse auf einem Server lauschen kann?

Das ist immer noch wahr.