*
   *  - "Strict": the cookie is omitted when the subject URL is an embedded resource or a
   *    potentially-destructive navigation.
   *
   *  - "Lax": the cookie is omitted when the subject URL is an embedded resource. It is sent for
   *    potentially-destructive navigation. This is the default value.
   *
   *  - "None": the cookie is always sent. The "Secure" attribute must also be set when setting this
   *    value.

 *
 * <ul>
 *   <li><b>Finite:</b> Many operations, such as {@link #length()} and {@link #read()}, will either
 *       block indefinitely or fail if the source creates an infinite reader.
 *   <li><b>Non-destructive:</b> A <i>destructive</i> reader will consume or otherwise alter the
 *       source as they are read from it. A source that provides such readers will not be reusable,

     *   attempt multiple proxy servers in sequence, eventually falling back to a direct
     *   connection.
     *
     * Set this to false to avoid retrying requests when doing so is destructive. In this case the
     * calling application should do its own recovery of connectivity failures.
     */
    fun retryOnConnectionFailure(retryOnConnectionFailure: Boolean) =
      apply {

* Missing null checks may cause NullPointerException
* Bridging with Kotlin code is polluted with platform types
* Some public APIs have incorrect nullability annotations (both overly restrictive and overly permissive)

While there are competing ways to represent absence (`Optional`, "Null Object" pattern, method overloads),
it is unlikely that we'll be able to remove `null` entirely.

* Specific HTTP headers or all of them with the wildcard `"*"`.

{* ../../docs_src/cors/tutorial001_py310.py hl[2,6:11,13:19] *}


The default parameters used by the `CORSMiddleware` implementation are restrictive by default, so you'll need to explicitly enable particular origins, methods, or headers, in order for browsers to be permitted to use them in a Cross-Domain context.

The following arguments are supported:

     * <p>
     * This method allows you to specify a custom ObjectInputFilter for fine-grained
     * control over which classes can be deserialized. Use this when the default filter
     * is too restrictive or permissive for your use case.
     * </p>
     *
     * @param bytes the byte array (must not be {@literal null})
     * @param filter the ObjectInputFilter to use, or null to disable filtering

            // Wait a bit for the processes to start
            Thread.sleep(50);

            // Destroy all processes
            processHelper.destroy();

            // Wait a bit for destruction to complete
            Thread.sleep(100);

            assertFalse(processHelper.isProcessRunning());
        } catch (Exception e) {
            fail("Unexpected exception: " + e.getMessage());
        }

<li>
	Similarly, if all types in <code>C</code>'s type set are
	channel types with the same element type and non-conflicting
	channel directions,
	and <code>P</code> has a known type argument <code>A</code>,
	the most restrictive channel type in <code>C</code>'s type
	set and <code>A</code> must unify loosely.
</li>
<li>
	If <code>P</code> does not have a known type argument
	and <code>C</code> contains exactly one type term <code>T</code>