Issue #6489 - fix RFC3986_UNAMBIGUOUS and UNSAFE UriCompliance modes.

Signed-off-by: Lachlan Roberts <lachlan@webtide.com>
jetty · Jul 1, 2021 · 76ab749 · 76ab749
1 parent b82b462
commit 76ab749
Showing 1 changed file with 3 additions and 2 deletions.
diff --git a/jetty-http/src/main/java/org/eclipse/jetty/http/UriCompliance.java b/jetty-http/src/main/java/org/eclipse/jetty/http/UriCompliance.java
@@ -13,8 +13,8 @@
 
 package org.eclipse.jetty.http;
 
-import java.util.Arrays;
 import java.util.EnumSet;
+import java.util.List;
 import java.util.Objects;
 import java.util.Set;
 import java.util.concurrent.atomic.AtomicInteger;
@@ -156,10 +156,11 @@ public String getDescription()
     public static final UriCompliance STRICT = new UriCompliance("STRICT", RFC3986.getAllowed());
 
     private static final AtomicInteger __custom = new AtomicInteger();
+    private static final List<UriCompliance> KNOWN_MODES = List.of(DEFAULT, LEGACY, RFC3986, RFC3986_UNAMBIGUOUS, UNSAFE, SAFE, STRICT);
 
     public static UriCompliance valueOf(String name)
     {
-        for (UriCompliance compliance : Arrays.asList(DEFAULT, LEGACY, RFC3986, RFC3986_UNAMBIGUOUS, UNSAFE, SAFE, STRICT))
+        for (UriCompliance compliance : KNOWN_MODES)
         {
             if (compliance.getName().equals(name))
                 return compliance;