Uploaded image for project: 'Tapestry'
  1. Tapestry
  2. TAPESTRY-1595

Add support for ignoring paths that belong to other servlets in the web application

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: 5.0.5
    • Fix Version/s: 5.0.8
    • Component/s: tapestry-core
    • Labels:
      None

      Description

      For pages not handled by Tapestry, it should pass control along to next filter in chain, which it does for paths that do not contain '.' or ':'. For example, if '/foo/bar' is not a page recognized by Tapestry, a URI with the path

      /foo/bar/image.gif

      will cause an 'IllegalArgumentException' with the message 'Unable to resolve page 'foo/bar/image' to a known page name. ...'

      while

      /foo/bar/image_gif

      will be properly forwarded to the filters after TapestryFilter.

      The problem seems to be that 'ComponentActionDispatcher' will attempt to process any path that contains '.' or ':', unlike 'PageRenderDispatcher' which explicitly checks that it recognizes a prefix of the path.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                hlship Howard M. Lewis Ship
                Reporter:
                dhauge Douglas Hauge
              • Votes:
                0 Vote for this issue
                Watchers:
                0 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: