You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Denis McCarthy (JIRA)" <de...@tapestry.apache.org> on 2008/01/10 16:05:34 UTC
[jira] Created: (TAPESTRY-2035) Optimized request paths seem to
cause problems with tapestry's default.css and related default assets for
relative URLs
Optimized request paths seem to cause problems with tapestry's default.css and related default assets for relative URLs
-----------------------------------------------------------------------------------------------------------------------
Key: TAPESTRY-2035
URL: https://issues.apache.org/jira/browse/TAPESTRY-2035
Project: Tapestry
Issue Type: Bug
Components: tapestry-core
Affects Versions: 5.0.8
Reporter: Denis McCarthy
This is related to TAPESTRY-2033. There seems to be (if I'm interpreting what I'm seeing correctly) caching of asset URLS for internal tapestry assets: for example
default.css, assets/tapestry/field-error-marker.png and so on. The URIS for these assets are cached the first time they are encountered. This causes a problem with
optimized request paths, because the cached path is optimized for the relative path at which the asset is first loaded by the browser. This means that if
the asset is referred to by a page in a different package, the URI is the original URI (optimized for where it was first encountered) leading to the
it being relative to the incorrect base path.
For example:
my login page is /myapp/login - on loading, default.css is optimized to ../tapestry/assets/default.css.
My next page is /myapp/alerts/view_alerts - default.css still points at ../tapestry/assets/default.css.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
[jira] Resolved: (TAPESTRY-2035) Optimized request paths seem to
cause problems with tapestry's default.css and related default assets for
relative URLs
Posted by "Denis McCarthy (JIRA)" <de...@tapestry.apache.org>.
[ https://issues.apache.org/jira/browse/TAPESTRY-2035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Denis McCarthy resolved TAPESTRY-2035.
--------------------------------------
Resolution: Fixed
Fix Version/s: 5.0.8
This is fixed now alright - thanks
> Optimized request paths seem to cause problems with tapestry's default.css and related default assets for relative URLs
> -----------------------------------------------------------------------------------------------------------------------
>
> Key: TAPESTRY-2035
> URL: https://issues.apache.org/jira/browse/TAPESTRY-2035
> Project: Tapestry
> Issue Type: Bug
> Components: tapestry-core
> Affects Versions: 5.0.8
> Reporter: Denis McCarthy
> Fix For: 5.0.8
>
>
> This is related to TAPESTRY-2033. There seems to be (if I'm interpreting what I'm seeing correctly) caching of asset URLS for internal tapestry assets: for example
> default.css, assets/tapestry/field-error-marker.png and so on. The URIS for these assets are cached the first time they are encountered. This causes a problem with
> optimized request paths, because the cached path is optimized for the relative path at which the asset is first loaded by the browser. This means that if
> the asset is referred to by a page in a different package, the URI is the original URI (optimized for where it was first encountered) leading to the
> it being relative to the incorrect base path.
> For example:
> my login page is /myapp/login - on loading, default.css is optimized to ../tapestry/assets/default.css.
> My next page is /myapp/alerts/view_alerts - default.css still points at ../tapestry/assets/default.css.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
[jira] Reopened: (TAPESTRY-2035) Optimized request paths seem to
cause problems with tapestry's default.css and related default assets for
relative URLs
Posted by "Howard M. Lewis Ship (JIRA)" <de...@tapestry.apache.org>.
[ https://issues.apache.org/jira/browse/TAPESTRY-2035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship reopened TAPESTRY-2035:
--------------------------------------------
Assignee: Howard M. Lewis Ship
> Optimized request paths seem to cause problems with tapestry's default.css and related default assets for relative URLs
> -----------------------------------------------------------------------------------------------------------------------
>
> Key: TAPESTRY-2035
> URL: https://issues.apache.org/jira/browse/TAPESTRY-2035
> Project: Tapestry
> Issue Type: Bug
> Components: tapestry-core
> Affects Versions: 5.0.8
> Reporter: Denis McCarthy
> Assignee: Howard M. Lewis Ship
> Fix For: 5.0.8
>
>
> This is related to TAPESTRY-2033. There seems to be (if I'm interpreting what I'm seeing correctly) caching of asset URLS for internal tapestry assets: for example
> default.css, assets/tapestry/field-error-marker.png and so on. The URIS for these assets are cached the first time they are encountered. This causes a problem with
> optimized request paths, because the cached path is optimized for the relative path at which the asset is first loaded by the browser. This means that if
> the asset is referred to by a page in a different package, the URI is the original URI (optimized for where it was first encountered) leading to the
> it being relative to the incorrect base path.
> For example:
> my login page is /myapp/login - on loading, default.css is optimized to ../tapestry/assets/default.css.
> My next page is /myapp/alerts/view_alerts - default.css still points at ../tapestry/assets/default.css.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
[jira] Closed: (TAPESTRY-2035) Optimized request paths seem to
cause problems with tapestry's default.css and related default assets for
relative URLs
Posted by "Howard M. Lewis Ship (JIRA)" <de...@tapestry.apache.org>.
[ https://issues.apache.org/jira/browse/TAPESTRY-2035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship closed TAPESTRY-2035.
------------------------------------------
Resolution: Invalid
Fix Version/s: (was: 5.0.8)
> Optimized request paths seem to cause problems with tapestry's default.css and related default assets for relative URLs
> -----------------------------------------------------------------------------------------------------------------------
>
> Key: TAPESTRY-2035
> URL: https://issues.apache.org/jira/browse/TAPESTRY-2035
> Project: Tapestry
> Issue Type: Bug
> Components: tapestry-core
> Affects Versions: 5.0.8
> Reporter: Denis McCarthy
> Assignee: Howard M. Lewis Ship
>
> This is related to TAPESTRY-2033. There seems to be (if I'm interpreting what I'm seeing correctly) caching of asset URLS for internal tapestry assets: for example
> default.css, assets/tapestry/field-error-marker.png and so on. The URIS for these assets are cached the first time they are encountered. This causes a problem with
> optimized request paths, because the cached path is optimized for the relative path at which the asset is first loaded by the browser. This means that if
> the asset is referred to by a page in a different package, the URI is the original URI (optimized for where it was first encountered) leading to the
> it being relative to the incorrect base path.
> For example:
> my login page is /myapp/login - on loading, default.css is optimized to ../tapestry/assets/default.css.
> My next page is /myapp/alerts/view_alerts - default.css still points at ../tapestry/assets/default.css.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
[jira] Commented: (TAPESTRY-2035) Optimized request paths seem to
cause problems with tapestry's default.css and related default assets for
relative URLs
Posted by "Howard M. Lewis Ship (JIRA)" <de...@tapestry.apache.org>.
[ https://issues.apache.org/jira/browse/TAPESTRY-2035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12561601#action_12561601 ]
Howard M. Lewis Ship commented on TAPESTRY-2035:
------------------------------------------------
Is this verified in 5.0.8, or in an earlier snapshot. I encountered and fixed this, I believe, while 5.0.8 was still a snapshot. Please verify using latest from trunk.
> Optimized request paths seem to cause problems with tapestry's default.css and related default assets for relative URLs
> -----------------------------------------------------------------------------------------------------------------------
>
> Key: TAPESTRY-2035
> URL: https://issues.apache.org/jira/browse/TAPESTRY-2035
> Project: Tapestry
> Issue Type: Bug
> Components: tapestry-core
> Affects Versions: 5.0.8
> Reporter: Denis McCarthy
>
> This is related to TAPESTRY-2033. There seems to be (if I'm interpreting what I'm seeing correctly) caching of asset URLS for internal tapestry assets: for example
> default.css, assets/tapestry/field-error-marker.png and so on. The URIS for these assets are cached the first time they are encountered. This causes a problem with
> optimized request paths, because the cached path is optimized for the relative path at which the asset is first loaded by the browser. This means that if
> the asset is referred to by a page in a different package, the URI is the original URI (optimized for where it was first encountered) leading to the
> it being relative to the incorrect base path.
> For example:
> my login page is /myapp/login - on loading, default.css is optimized to ../tapestry/assets/default.css.
> My next page is /myapp/alerts/view_alerts - default.css still points at ../tapestry/assets/default.css.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org