*
     * Unfortunately, we don't distinguish between these two cases in our public API: Joiner.on(...)
     * and Joiner.on(...).useForNull(...) both declare the same return type: plain Joiner. To ensure
     * that users *can* pass null arguments to Joiner, we annotate it as if it always tolerates null
     * inputs, rather than as if it never tolerates them.
     *

        facetQueryView.setTitle("test");
        viewHelper.addFacetQueryView(facetQueryView);
        assertTrue(viewHelper.getFacetQueryViewList().contains(facetQueryView));

        viewHelper.addInlineMimeType("text/plain");

        assertNotNull(viewHelper.getActionHook());

        ViewHelper.ActionHook actionHook = new ViewHelper.ActionHook();
        viewHelper.setActionHook(actionHook);

crawler.document.cache.enabled=true
# Maximum size (bytes) for document cache.
crawler.document.cache.max.size=2621440
# Supported MIME types for document cache.
crawler.document.cache.supported.mimetypes=text/html

         * However, we don't expose currentFuture to users, so they can't attach listeners. And the
         * Future might not even be a ListenableFuture, just a plain Future. That said, similar
         * problems can exist with methods like FutureTask.done(), not to mention slow calls to
         * Thread.interrupt() (as discussed in InterruptibleTask). At the end of the day, it's

  fun getContentTypeConnects() {
    server.enqueue(
      MockResponse(
        headers = headersOf("Content-Type", "text/plain"),
        body = "ABC",
      ),
    )
    val response = getResponse(newRequest("/"))
    assertThat(response.body.contentType()).isEqualTo(
      "text/plain".toMediaType(),
    )
    response.body.close()
  }

  @Test
  fun getContentEncodingConnects() {

         * However, we don't expose currentFuture to users, so they can't attach listeners. And the
         * Future might not even be a ListenableFuture, just a plain Future. That said, similar
         * problems can exist with methods like FutureTask.done(), not to mention slow calls to
         * Thread.interrupt() (as discussed in InterruptibleTask). At the end of the day, it's

    /** The key of the configuration. e.g. true */
    String RESPONSE_HIGHLIGHT_content_title_ENABLED = "response.highlight.content_title.enabled";

    /** The key of the configuration. e.g. application/pdf,text/plain */
    String RESPONSE_INLINE_MIMETYPES = "response.inline.mimetypes";

    /** The key of the configuration. e.g. text/html=X-XSS-Protection: 1; mode=block<br>
     * text/html=Content-Security-Policy: reflected-xss block<br>

  }

  /*
   * Tests that we workaround GWT bug #3621 (or that it is already fixed).
   *
   * A call to of() with a parameter that is not a plain Object[] (here,
   * Interface[]) creates a RegularImmutableSortedSet backed by an array of that
   * type. Later, RegularImmutableSortedSet.toArray() calls System.arraycopy()

 * Benchmarks (as of December 2011) show that:
 *
 * <ul>
 *   <li>for an unnested {@code lock()} and {@code unlock()}, a cycle detecting lock takes 38ns as
 *       opposed to the 24ns taken by a plain lock.
 *   <li>for nested locking, the cost increases with the depth of the nesting:
 *       <ul>
 *         <li>2 levels: average of 64ns per lock()/unlock()
 *         <li>3 levels: average of 77ns per lock()/unlock()

     *
     * 1. We'll want to use something like @PolyNull once we can make that work for the various
     * platforms we target.
     *
     * 2. Kotlin's Map type has a getOrDefault method that accepts and returns a "plain V," in
     * contrast to the "V?" type that we're using. As a result, Kotlin sees a conflict between the
     * nullness annotations in ImmutableMap and those in its own Map type. In response, it considers