[
https://issues.apache.org/jira/browse/OOZIE-1883?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shwetha G S updated OOZIE-1883:
-------------------------------
Fix Version/s: (was: trunk)
> hostnameFilter has invalid url-pattern
> --------------------------------------
>
> Key: OOZIE-1883
> URL: https://issues.apache.org/jira/browse/OOZIE-1883
> Project: Oozie
> Issue Type: Bug
> Affects Versions: 3.3.2, 4.0.1
> Environment: IBM WebSphere Liberty Profile
> Reporter: David Villegas
> Assignee: David Villegas
> Fix For: 4.1.0
>
> Attachments: OOZIE-1883.patch
>
>
> The hostnameFilter in web-common.xml is currently:
> {code:xml}
> <filter-mapping>
> <filter-name>hostnameFilter</filter-name>
> <url-pattern>*</url-pattern>
> </filter-mapping>
> {code}
> However, '*' is not a valid url-pattern. From the servlet 2.5 spec:
> {quote}
> In the Web application deployment descriptor, the following syntax is used to
> define mappings:
> * A string beginning with a ‘/’ character and ending with a ‘/*’ suffix is
> used
> for path mapping.
> * A string beginning with a ‘*.’ prefix is used as an extension mapping.
> * A string containing only the ’/’ character indicates the "default" servlet
> of
> the application. In this case the servlet path is the request URI minus the
> context path and the path info is null.
> * All other strings are used for exact matches only.
> {quote}
> This causes the filter to not be applied correctly in some application
> servers such as WASLP
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
