This is an automated email from the ASF dual-hosted git repository.
asf-gitbox-commits pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/struts-site.git
The following commit(s) were added to refs/heads/asf-site by this push:
new 1098fa83e2 Automatic Site Publish by Buildbot
1098fa83e2 is described below
commit 1098fa83e298df9c9de2d1839debc4bc8e9d40d6
Author: buildbot <[email protected]>
AuthorDate: Sat Oct 10 12:51:09 2026 +0000
Automatic Site Publish by Buildbot
---
output/core-developers/wildcard-mappings.html | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/output/core-developers/wildcard-mappings.html
b/output/core-developers/wildcard-mappings.html
index 8caf6db748..1e4cf249c6 100644
--- a/output/core-developers/wildcard-mappings.html
+++ b/output/core-developers/wildcard-mappings.html
@@ -185,7 +185,7 @@ replacing <code class="language-plaintext
highlighter-rouge">{1}</code>. For the
the new values.</p>
<p>Mappings are matched against the request in the order they appear in the
frameworkâs configuration file. If more than
-one pattern matches <strong>the last one wins</strong>, so less specific
patterns must appear before more specific ones. However,
+one pattern matches <strong>the first one wins</strong>, so more specific
patterns must appear before less specific ones. However,
if the request URL can be matched against a path without any wildcards in it,
no wildcard matching is performed
and order is not important. Also, note that wildcards are not greedy, meaning
they only match until the first
occurrence of the following string pattern. For example, consider the
following mapping:</p>
