SEC-2256: Fix intercept-url doc precidence statement
Previously the documentation incorrectly stated "If a request matches multiple patterns, the method-specific match will take precedence regardless of ordering." This has now been removed and InterceptUrlConfigTests was added previously to ensure this was true.
This commit is contained in:
parent
be8aad8306
commit
e5804d323b
|
@ -173,8 +173,7 @@
|
||||||
put the most specific matches at the top. You can also add a
|
put the most specific matches at the top. You can also add a
|
||||||
<literal>method</literal> attribute to limit the match to a particular HTTP
|
<literal>method</literal> attribute to limit the match to a particular HTTP
|
||||||
method (<literal>GET</literal>, <literal>POST</literal>, <literal>PUT</literal>
|
method (<literal>GET</literal>, <literal>POST</literal>, <literal>PUT</literal>
|
||||||
etc.). If a request matches multiple patterns, the method-specific match will
|
etc.).</para>
|
||||||
take precedence regardless of ordering.</para>
|
|
||||||
</note>
|
</note>
|
||||||
<para> To add some users, you can define a set of test data directly in the namespace: <programlisting language="xml"><![CDATA[
|
<para> To add some users, you can define a set of test data directly in the namespace: <programlisting language="xml"><![CDATA[
|
||||||
<authentication-manager>
|
<authentication-manager>
|
||||||
|
|
Loading…
Reference in New Issue