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

   * for cross-language compatibility. For other use cases, prefer {@link #putUnencodedChars}, which
   * is faster, produces the same output across Java releases, and processes every {@code char} in
   * the input, even if some are invalid.
   */
  @CanIgnoreReturnValue
  PrimitiveSink putString(CharSequence charSequence, Charset charset);

import org.lastaflute.web.response.HtmlResponse;
import org.lastaflute.web.response.StreamResponse;

import jakarta.annotation.Resource;

/**
 * Action class for handling document redirection requests.
 * This action processes "go" requests that redirect users to specific documents
 * while tracking click events and handling various URL types including file system paths.
 */
public class GoAction extends FessSearchAction {

    /**

    @Resource
    private FailureUrlService failureUrlService;
    @Resource
    private FailureUrlPager failureUrlPager;
    /** Helper for managing crawler processes */
    @Resource
    protected ProcessHelper processHelper;

    // ===================================================================================

    //                                                                           =========
    @Resource
    private CrawlingInfoService crawlingInfoService;

    /** Helper for managing crawling processes and session information */
    @Resource
    protected ProcessHelper processHelper;

    // ===================================================================================

- how to deal with resolution from different places like local/remote/workspace
- how to incorporate the metadata processor to start with
- create a hook to programmatically configure the test
- create a plugin processor
- directory
- jar
- hooks for loading

- I could make an annotation that marked another class as its plugin discoverer, I could just add it to

    "unitTests": true,
    "functionalTests": false,
    "crossVersionTests": false
  },
  {
    "name": "internal-instrumentation-processor",
    "path": "platforms/core-runtime/internal-instrumentation-processor",
    "unitTests": true,
    "functionalTests": false,
    "crossVersionTests": false
  },
  {
    "name": "internal-integ-testing",

        if (logger.isDebugEnabled()) {
            logger.debug("Storing state in session: {}", stateData);
        }
        stateMap.put(state, stateData);
    }

    /**
     * Processes authentication data from the OAuth2 callback.
     * @param request The HTTP servlet request containing authentication data.
     * @return The login credential or null if processing fails.
     */

## Let's Encrypt

Avant Let's Encrypt, ces certificats HTTPS étaient vendus par des tiers de confiance.

Le processus d'acquisition d'un de ces certificats était auparavant lourd, nécessitait pas mal de paperasses et les certificats étaient assez chers.

func TestRaulStatsRaceCondition(t *testing.T) {
	httpStats := newHTTPStats()
	// Simulate the concurrent scenario from the original race condition:
	// Multiple HTTP request handlers updating stats concurrently,
	// while background processes are reading the stats for persistence.
	const numWriters = 100 // Simulate many HTTP request handlers.
	const numReaders = 50  // Simulate background stats readers.
	const opsPerGoroutine = 100

	var wg sync.WaitGroup