Tapestry 5
  1. Tapestry 5
  2. TAP5-1042

URLRewriting causes confusion about the incoming Request path, leading to incorrect optimized relative URLs

    Details

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

      Description

      This may only be an issue where the URLRewriter logic, but it appears that the RequestPathOptimizer gets confused when the path significantly changed, and ends up generating incorrect relative URLs. I've had to turn request path optimization off for my client where they want all T5 page and component events to be prefixed with "/t5".

        Issue Links

          Activity

          Hide
          Hudson added a comment -

          Integrated in tapestry-5.2-freestyle #128 (See http://hudson.zones.apache.org/hudson/job/tapestry-5.2-freestyle/128/)

          Show
          Hudson added a comment - Integrated in tapestry-5.2-freestyle #128 (See http://hudson.zones.apache.org/hudson/job/tapestry-5.2-freestyle/128/ )

            People

            • Assignee:
              Howard M. Lewis Ship
              Reporter:
              Howard M. Lewis Ship
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development