Jetty 11.0.1 fails test with 400 - Ambiguous segment in URI (when this was previously 200)

[rbygrave]

Refer jetty/jetty.project#6001

For jetty-10 and beyond, the default is changed to disallow all three. It is now configurable in a new UriCompliance class that can be set on HttpConfiguration

// RouteSplatTest

  @Test
  void when_utf8Encoded() {
    String path = URLEncoder.encode("java/kotlin", StandardCharsets.UTF_8)
      + "/two/" + URLEncoder.encode("x/y", StandardCharsets.UTF_8);

    HttpResponse<String> res = pair.request().path(path).get().asString();

    assertThat(res.body()).isEqualTo("splats:[java/kotlin, x/y]");
    assertThat(res.statusCode()).isEqualTo(200);
  }

[rbygrave]

The point being that URL encoding of / makes it ambiguous and that isn't allowed by default with Jetty 11.0.1+

At this point from a Jex perspective this is fine. If people are requiring the old behavior they would need to configure Jetty via UriCompliance back to the legacy behavior.

Summary

In summary, we will change the Jex test and move forward with the default jetty 11.0.1 behavior as the expected behavior.