You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tapestry.apache.org by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org> on 2010/03/03 22:02:27 UTC

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

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.


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

Posted by "Hudson (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/TAP5-1042?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12875068#action_12875068 ] 

Hudson commented on TAP5-1042:
------------------------------

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

> 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
>            Assignee: 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.


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

Posted by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/TAP5-1042?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Howard M. Lewis Ship reassigned TAP5-1042:
------------------------------------------

    Assignee: Howard M. Lewis Ship

> 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
>            Assignee: 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.


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

Posted by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/TAP5-1042?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Howard M. Lewis Ship closed TAP5-1042.
--------------------------------------

    Fix Version/s: 5.2.0
       Resolution: Fixed

> 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
>            Assignee: Howard M. Lewis Ship
>             Fix For: 5.2.0
>
>
> 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.


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

Posted by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/TAP5-1042?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Howard M. Lewis Ship closed TAP5-1042.
--------------------------------------

    Fix Version/s: 5.2.0
       Resolution: Fixed

> 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
>            Assignee: Howard M. Lewis Ship
>             Fix For: 5.2.0
>
>
> 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.


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

Posted by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/TAP5-1042?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Howard M. Lewis Ship reassigned TAP5-1042:
------------------------------------------

    Assignee: Howard M. Lewis Ship

> 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
>            Assignee: 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.


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

Posted by "Hudson (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/TAP5-1042?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12875068#action_12875068 ] 

Hudson commented on TAP5-1042:
------------------------------

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

> 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
>            Assignee: 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.