[TAP5-1042] URLRewriting causes confusion about the incoming Request path, leading to incorrect optimized relative URLs

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 5.2.0
• Fix Version/s: 5.2.0
• Component/s: tapestry-core
• Assignee: Howard Lewis Ship
• Reporter: Howard Lewis Ship
• Created: 03/Mar/10 21:00
• Updated: 02/Jul/10 17:25
• Resolved: 02/Jul/10 17:25

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

• incorporates: TAP5-954 URLRewriting only applys to component event and page render requests, not to asset requests