Tapestry 5
  1. Tapestry 5
  2. TAP5-2070

Respond with a HTTP 404 if the page is activated with an activation context not explicitly supported by the page itself

    Details

    • Type: Improvement Improvement
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 5.4
    • Fix Version/s: 5.4
    • Component/s: tapestry-core
    • Labels:
      None

      Description

      The behavior from day one for pages within Tapestry is to being able to serve requests that come with an activation context with more parameters that the ones declared by the page itself.

      This feature lead the framework to serve requests that comes to URL which are not explicitly declared by the pages, for example a page named: Super with an activation event handler method like this one:

      onActivate(String character)

      { ... }

      will finely serve requests for:

      /super/mario
      /super/luigi
      /super/wario
      /super/waluigi

      but it will also serve requests for:

      /super/mario/luigi/wario/waluigi

      This issue is to change that behavior.
      If the page does declare a specific activation event handler method the corresponding serving URLs should adhere strictly, otherwise a HTTP 404 is raised.

        Issue Links

          Activity

            People

            • Assignee:
              Massimo Lusetti
              Reporter:
              Massimo Lusetti
            • Votes:
              3 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development