Uploaded image for project: 'Tapestry 5'
  1. Tapestry 5
  2. TAP5-1042

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

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Fixed
    • 5.2.0
    • 5.2.0
    • tapestry-core
    • 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".

      Attachments

        Issue Links

          Activity

            People

              hlship Howard Lewis Ship
              hlship Howard Lewis Ship
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: