You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Thiago H. de Paula Figueiredo (JIRA)" <de...@tapestry.apache.org> on 2007/11/30 17:44:43 UTC
[jira] Created: (TAPESTRY-1947) Requests to non-existent pages URLs
with extensions
Requests to non-existent pages URLs with extensions
---------------------------------------------------
Key: TAPESTRY-1947
URL: https://issues.apache.org/jira/browse/TAPESTRY-1947
Project: Tapestry
Issue Type: Bug
Components: tapestry-core
Affects Versions: 5.0.6
Reporter: Thiago H. de Paula Figueiredo
Quick summary: Tapestry 5.0.6 doesn't check the existence of a page when an URL which looks like an action request is requested (any url that has a period).
Long description:
If I request the page /xxx, where xxx is a non-existing page, T5 raises a
standard HTTP 404 error that I'm able to catch through the <error-page>
tag in my web.xml. So far, so good.
If I request the page /xxx.html, where xxx is a non-existing page, T5 does
not raise a 404 error: it throws an IllegalArgumentException:
java.lang.IllegalArgumentException: Unable to resolve 'cursos/id10' to a
known page name. Available page names: [list of my Tapestry pages].
at
org.apache.tapestry.internal.services.ComponentClassResolverImpl$8.invoke(ComponentClassResolverImpl.java:417)
at
org.apache.tapestry.internal.services.ComponentClassResolverImpl$8.invoke(ComponentClassResolverImpl.java:412)
at
org.apache.tapestry.ioc.internal.util.ConcurrentBarrier.withRead(ConcurrentBarrier.java:77)
at
org.apache.tapestry.internal.services.ComponentClassResolverImpl.canonicalizePageName(ComponentClassResolverImpl.java:410)
at
$ComponentClassResolver_1166cebf61d.canonicalizePageName($ComponentClassResolver_1166cebf61d.java)
at
org.apache.tapestry.internal.services.PagePoolImpl.checkout(PagePoolImpl.java:59)
[snip]
It looks like non-existent pages checks are done with normal page
requests, but not with action requests.
--
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-1947) Mangled URLs that should result in
standard 404 error pages are instead resulting in a Tapestry exception
report
Posted by "Howard M. Lewis Ship (JIRA)" <de...@tapestry.apache.org>.
[ https://issues.apache.org/jira/browse/TAPESTRY-1947?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship closed TAPESTRY-1947.
------------------------------------------
Resolution: Fixed
Fix Version/s: 5.0.7
> Mangled URLs that should result in standard 404 error pages are instead resulting in a Tapestry exception report
> ----------------------------------------------------------------------------------------------------------------
>
> Key: TAPESTRY-1947
> URL: https://issues.apache.org/jira/browse/TAPESTRY-1947
> Project: Tapestry
> Issue Type: Bug
> Components: tapestry-core
> Affects Versions: 5.0.6
> Reporter: Thiago H. de Paula Figueiredo
> Assignee: Howard M. Lewis Ship
> Fix For: 5.0.7
>
>
> Quick summary: Tapestry 5.0.6 doesn't check the existence of a page when an URL which looks like an action request is requested (any url that has a period).
> Long description:
> If I request the page /xxx, where xxx is a non-existing page, T5 raises a
> standard HTTP 404 error that I'm able to catch through the <error-page>
> tag in my web.xml. So far, so good.
> If I request the page /xxx.html, where xxx is a non-existing page, T5 does
> not raise a 404 error: it throws an IllegalArgumentException:
> java.lang.IllegalArgumentException: Unable to resolve 'cursos/id10' to a
> known page name. Available page names: [list of my Tapestry pages].
> at
> org.apache.tapestry.internal.services.ComponentClassResolverImpl$8.invoke(ComponentClassResolverImpl.java:417)
> at
> org.apache.tapestry.internal.services.ComponentClassResolverImpl$8.invoke(ComponentClassResolverImpl.java:412)
> at
> org.apache.tapestry.ioc.internal.util.ConcurrentBarrier.withRead(ConcurrentBarrier.java:77)
> at
> org.apache.tapestry.internal.services.ComponentClassResolverImpl.canonicalizePageName(ComponentClassResolverImpl.java:410)
> at
> $ComponentClassResolver_1166cebf61d.canonicalizePageName($ComponentClassResolver_1166cebf61d.java)
> at
> org.apache.tapestry.internal.services.PagePoolImpl.checkout(PagePoolImpl.java:59)
> [snip]
> It looks like non-existent pages checks are done with normal page
> requests, but not with action requests.
--
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] Assigned: (TAPESTRY-1947) Requests to non-existent pages
URLs with extensions
Posted by "Howard M. Lewis Ship (JIRA)" <de...@tapestry.apache.org>.
[ https://issues.apache.org/jira/browse/TAPESTRY-1947?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship reassigned TAPESTRY-1947:
----------------------------------------------
Assignee: Howard M. Lewis Ship
> Requests to non-existent pages URLs with extensions
> ---------------------------------------------------
>
> Key: TAPESTRY-1947
> URL: https://issues.apache.org/jira/browse/TAPESTRY-1947
> Project: Tapestry
> Issue Type: Bug
> Components: tapestry-core
> Affects Versions: 5.0.6
> Reporter: Thiago H. de Paula Figueiredo
> Assignee: Howard M. Lewis Ship
>
> Quick summary: Tapestry 5.0.6 doesn't check the existence of a page when an URL which looks like an action request is requested (any url that has a period).
> Long description:
> If I request the page /xxx, where xxx is a non-existing page, T5 raises a
> standard HTTP 404 error that I'm able to catch through the <error-page>
> tag in my web.xml. So far, so good.
> If I request the page /xxx.html, where xxx is a non-existing page, T5 does
> not raise a 404 error: it throws an IllegalArgumentException:
> java.lang.IllegalArgumentException: Unable to resolve 'cursos/id10' to a
> known page name. Available page names: [list of my Tapestry pages].
> at
> org.apache.tapestry.internal.services.ComponentClassResolverImpl$8.invoke(ComponentClassResolverImpl.java:417)
> at
> org.apache.tapestry.internal.services.ComponentClassResolverImpl$8.invoke(ComponentClassResolverImpl.java:412)
> at
> org.apache.tapestry.ioc.internal.util.ConcurrentBarrier.withRead(ConcurrentBarrier.java:77)
> at
> org.apache.tapestry.internal.services.ComponentClassResolverImpl.canonicalizePageName(ComponentClassResolverImpl.java:410)
> at
> $ComponentClassResolver_1166cebf61d.canonicalizePageName($ComponentClassResolver_1166cebf61d.java)
> at
> org.apache.tapestry.internal.services.PagePoolImpl.checkout(PagePoolImpl.java:59)
> [snip]
> It looks like non-existent pages checks are done with normal page
> requests, but not with action requests.
--
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] Updated: (TAPESTRY-1947) Mangled URLs that should result in
standard 404 error pages are instead resulting in a Tapestry exception
report
Posted by "Howard M. Lewis Ship (JIRA)" <de...@tapestry.apache.org>.
[ https://issues.apache.org/jira/browse/TAPESTRY-1947?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship updated TAPESTRY-1947:
-------------------------------------------
Summary: Mangled URLs that should result in standard 404 error pages are instead resulting in a Tapestry exception report (was: Requests to non-existent pages URLs with extensions)
> Mangled URLs that should result in standard 404 error pages are instead resulting in a Tapestry exception report
> ----------------------------------------------------------------------------------------------------------------
>
> Key: TAPESTRY-1947
> URL: https://issues.apache.org/jira/browse/TAPESTRY-1947
> Project: Tapestry
> Issue Type: Bug
> Components: tapestry-core
> Affects Versions: 5.0.6
> Reporter: Thiago H. de Paula Figueiredo
> Assignee: Howard M. Lewis Ship
> Fix For: 5.0.7
>
>
> Quick summary: Tapestry 5.0.6 doesn't check the existence of a page when an URL which looks like an action request is requested (any url that has a period).
> Long description:
> If I request the page /xxx, where xxx is a non-existing page, T5 raises a
> standard HTTP 404 error that I'm able to catch through the <error-page>
> tag in my web.xml. So far, so good.
> If I request the page /xxx.html, where xxx is a non-existing page, T5 does
> not raise a 404 error: it throws an IllegalArgumentException:
> java.lang.IllegalArgumentException: Unable to resolve 'cursos/id10' to a
> known page name. Available page names: [list of my Tapestry pages].
> at
> org.apache.tapestry.internal.services.ComponentClassResolverImpl$8.invoke(ComponentClassResolverImpl.java:417)
> at
> org.apache.tapestry.internal.services.ComponentClassResolverImpl$8.invoke(ComponentClassResolverImpl.java:412)
> at
> org.apache.tapestry.ioc.internal.util.ConcurrentBarrier.withRead(ConcurrentBarrier.java:77)
> at
> org.apache.tapestry.internal.services.ComponentClassResolverImpl.canonicalizePageName(ComponentClassResolverImpl.java:410)
> at
> $ComponentClassResolver_1166cebf61d.canonicalizePageName($ComponentClassResolver_1166cebf61d.java)
> at
> org.apache.tapestry.internal.services.PagePoolImpl.checkout(PagePoolImpl.java:59)
> [snip]
> It looks like non-existent pages checks are done with normal page
> requests, but not with action requests.
--
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