Uploaded image for project: 'Oozie'
  1. Oozie
  2. OOZIE-1883

hostnameFilter has invalid url-pattern

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 3.3.2, 4.0.1
    • Fix Version/s: 4.1.0
    • Component/s: None
    • Labels:
      None
    • Environment:

      IBM WebSphere Liberty Profile

      Description

      The hostnameFilter in web-common.xml is currently:

      <filter-mapping>
          <filter-name>hostnameFilter</filter-name>
          <url-pattern>*</url-pattern>
      </filter-mapping>
      

      However, '*' is not a valid url-pattern. From the servlet 2.5 spec:

      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.

      This causes the filter to not be applied correctly in some application servers such as WASLP

        Attachments

        1. OOZIE-1883.patch
          0.8 kB
          David Villegas

          Activity

            People

            • Assignee:
              dvillegas David Villegas
              Reporter:
              dvillegas David Villegas
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: