Update filters documentation

Fixes: gh-5553
This commit is contained in:
Denis Babochenko 2019-04-01 22:07:11 +03:00 committed by Josh Cummings
parent bed3371b80
commit 21f7148e7a
3 changed files with 0 additions and 26 deletions

View File

@ -364,9 +364,6 @@ intercept-url.attlist &=
## The HTTP Method for which the access configuration attributes should apply. If not specified, the attributes will apply to any method.
attribute method {"GET" | "DELETE" | "HEAD" | "OPTIONS" | "POST" | "PUT" | "PATCH" | "TRACE"}?
intercept-url.attlist &=
## The filter list for the path. Currently can be set to "none" to remove a path from having any filters applied. The full filter stack (consisting of all filters created by the namespace configuration, and any added using 'custom-filter'), will be applied to any other paths.
attribute filters {"none"}?
intercept-url.attlist &=
## Used to specify that a URL must be accessed over http or https, or that there is no preference. The value should be "http", "https" or "any", respectively.
attribute requires-channel {xsd:token}?

View File

@ -1284,20 +1284,6 @@
</xs:restriction>
</xs:simpleType>
</xs:attribute>
<xs:attribute name="filters">
<xs:annotation>
<xs:documentation>The filter list for the path. Currently can be set to "none" to remove a path from having
any filters applied. The full filter stack (consisting of all filters created by the
namespace configuration, and any added using 'custom-filter'), will be applied to any
other paths.
</xs:documentation>
</xs:annotation>
<xs:simpleType>
<xs:restriction base="xs:token">
<xs:enumeration value="none"/>
</xs:restriction>
</xs:simpleType>
</xs:attribute>
<xs:attribute name="requires-channel" type="xs:token">
<xs:annotation>
<xs:documentation>Used to specify that a URL must be accessed over http or https, or that there is no

View File

@ -950,15 +950,6 @@ Lists the access attributes which will be stored in the `FilterInvocationSecurit
This should be a comma-separated list of the security configuration attributes (such as role names).
[[nsa-intercept-url-filters]]
* **filters**
Can only take the value "none".
This will cause any matching request to bypass the Spring Security filter chain entirely.
None of the rest of the `<http>` configuration will have any effect on the request and there will be no security context available for its duration.
Access to secured methods during the request will fail.
NOTE: This property is invalid for <<nsa-filter-security-metadata-source,filter-security-metadata-source>>
[[nsa-intercept-url-method]]
* **method**
The HTTP Method which will be used in combination with the pattern and servlet path (optional) to match an incoming request.