assertThrows(IllegalArgumentException.class, () -> range.gap(Range.closed(4, 6)));
    assertThrows(IllegalArgumentException.class, () -> range.gap(Range.closed(2, 4)));
    assertThrows(IllegalArgumentException.class, () -> range.gap(Range.closed(2, 3)));
  }

  public void testGap_invalidRangesWithInfinity() {
    assertThrows(IllegalArgumentException.class, () -> Range.atLeast(1).gap(Range.atLeast(2)));

    assertThrows(IllegalArgumentException.class, () -> range.gap(Range.closed(4, 6)));
    assertThrows(IllegalArgumentException.class, () -> range.gap(Range.closed(2, 4)));
    assertThrows(IllegalArgumentException.class, () -> range.gap(Range.closed(2, 3)));
  }

  public void testGap_invalidRangesWithInfinity() {
    assertThrows(IllegalArgumentException.class, () -> Range.atLeast(1).gap(Range.atLeast(2)));

OkHttp is principled and avoids being overly configurable, especially when such configuration is
to workaround a buggy server, test invalid scenarios or that contradict the relevant RFC.
Other HTTP libraries exist that fill that gap allowing extensive customisation including potentially
invalid requests.

Example Limitations

* Does not allow GET with a body.
* Cache is not an interface with alternative implementations.

Get a URL
---------