URLRewriting causes confusion about the incoming Request path, leading to
incorrect optimized relative URLs
-----------------------------------------------------------------------------------------------------------
Key: TAP5-1042
URL: https://issues.apache.org/jira/browse/TAP5-1042
Project: Tapestry 5
Issue Type: Bug
Components: tapestry-core
Affects Versions: 5.2.0
Reporter: Howard M. Lewis Ship
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".
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
