You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tapestry.apache.org by immutability <de...@bielik.org> on 2009/06/15 20:46:04 UTC
T5.1: Custom Acegi 403 error page breaks page/actionlinks
Guys, I'm facing another strange issue with Tapestry 5.1.0.5. I'm using
Tapestry-Acegi, but I guess I would get the same behavior with
Spring-Security. I have configured a custom error page for the 403 forbidden
error in my AppModule, i.e.:
configuration.add("acegi.accessDenied.url", "/AccessDenied");
So far so good. When I manually open a secured page while logged in as a
user without the required privilege, instead of getting the plain white 403
page, I'll get a nice Access Denied page with explanation, etc. But while a
page with address /AccessDenied is displayed (i.e.
http://127.0.0.1/AccessDenied), the browser displays the URL of the original
forbidden page (e.g. http://127.0.0.1/User/Create).
This would actually be quite nice, but I think it is causing that both
pagelinks and actionlinks will break, as if Tapestry failed to generate
proper target URLs for them. Imagine I have a "logout" action link within my
Border component - the Border component is also used on the custom
AccessDenied page to get the consistent look with the rest of the webapp.
Normally, the URL that is generated for this action link will depend on the
page I'm viewing, so for example:
http://127.0.0.1/index.border.logout (on the /Index page)
http://127.0.0.1/user/create.border.logout (on the /User/Create page)
But if I try to access the Create User page without the privileges and get
the access denied page, the actionlink's target URL will look like this:
http://127.0.0.1/user/accessdenied.border.logout (on the /User/Create page)
Obviously, this won't work, because there's no AccessDenied page under /user
- it is only in the root of the webapp. Similarly, a pagelink targeting
language configuration page, declared as:
<t:pagelink page="language"/>
doesn't work, because it generates this target URL:
http://127.0.0.1/user/language
instead of the correct form:
http://127.0.0.1/language
Is this a bug within Tapestry related to server side request forwarding or
am I missing something? I'm getting the same behavior in Jetty and in Tomcat
6.0.18.
Thanks,
Rado
--
View this message in context: http://www.nabble.com/T5.1%3A-Custom-Acegi-403-error-page-breaks-page-actionlinks-tp24040558p24040558.html
Sent from the Tapestry - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: T5.1: Request forwarding breaks page/actionlinks
Posted by immutability <de...@bielik.org>.
The problem I have described in my original message is not related to
Acegi/Spring, but it appears to be a problem in the way Tapestry generates
URLs for ActionLinks and PageLinks after an server-side request forward is
performed. Unlike a client-side redirect, in this case the URL that the
browser sees doesn't change to the URL of the new page. This is exactly what
Acegi does if it has the acegi.accessDenied.url property specified, but you
can also do a forward manually using RequestDispatcher.
Now, is this a bug in Tapestry? I couldn't find anything in JIRA.
Imagine the following scenario: a page with a logical address /user/create
which does nothing else but a forward (in onActivate) to /test. The result
is that the /test page will be displayed, but the /user/create page's URL
will be shown in the browser's address bar. As a consequence, Tapestry will
generate relative URLs for all PageLinks and ActionLinks as if it was on the
/test page, but these links will be relative to the /user/create page - and
thus invalid. I can provide a sample code to reproduce.
Thanks,
Rado
immutability wrote:
>
> Guys, I'm facing another strange issue with Tapestry 5.1.0.5. I'm using
> Tapestry-Acegi, but I guess I would get the same behavior with
> Spring-Security. I have configured a custom error page for the 403
> forbidden error in my AppModule, i.e.:
> configuration.add("acegi.accessDenied.url", "/AccessDenied");
>
> So far so good. When I manually open a secured page while logged in as a
> user without the required privilege, instead of getting the plain white
> 403 page, I'll get a nice Access Denied page with explanation, etc. But
> while a page with address /AccessDenied is displayed (i.e.
> http://127.0.0.1/AccessDenied), the browser displays the URL of the
> original forbidden page (e.g. http://127.0.0.1/User/Create).
>
> This would actually be quite nice, but I think it is causing that both
> pagelinks and actionlinks will break, as if Tapestry failed to generate
> proper target URLs for them. Imagine I have a "logout" action link within
> my Border component - the Border component is also used on the custom
> AccessDenied page to get the consistent look with the rest of the webapp.
> Normally, the URL that is generated for this action link will depend on
> the page I'm viewing, so for example:
> http://127.0.0.1/index.border.logout (on the /Index page)
> http://127.0.0.1/user/create.border.logout (on the /User/Create page)
>
> But if I try to access the Create User page without the privileges and get
> the access denied page, the actionlink's target URL will look like this:
> http://127.0.0.1/user/accessdenied.border.logout (on the /User/Create
> page)
>
> Obviously, this won't work, because there's no AccessDenied page under
> /user - it is only in the root of the webapp. Similarly, a pagelink
> targeting language configuration page, declared as:
> <t:pagelink page="language"/>
>
> doesn't work, because it generates this target URL:
> http://127.0.0.1/user/language
>
> instead of the correct form:
> http://127.0.0.1/language
>
> Is this a bug within Tapestry related to server side request forwarding or
> am I missing something? I'm getting the same behavior in Jetty and in
> Tomcat 6.0.18.
>
> Thanks,
> Rado
>
--
View this message in context: http://www.nabble.com/T5.1%3A-Request-forwarding-breaks-page-actionlinks-tp24040558p24054631.html
Sent from the Tapestry - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: T5.1: Request forwarding breaks page/actionlinks
Posted by "Thiago H. de Paula Figueiredo" <th...@gmail.com>.
Em Sat, 21 Nov 2009 13:23:35 -0200, Kalle Korhonen
<ka...@gmail.com> escreveu:
> Ah great, there's such a symbol! Nevertheless, you don't think that
> the components should use PageRenderLinkSource for creating links?
Yes. Their sources should be updated, as PageRenderLinkSource was
introduced in T5.1.
--
Thiago H. de Paula Figueiredo
Independent Java, Apache Tapestry 5 and Hibernate consultant, developer,
and instructor
Owner, software architect and developer, Ars Machina Tecnologia da
Informação Ltda.
http://www.arsmachina.com.br
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: T5.1: Request forwarding breaks page/actionlinks
Posted by Kalle Korhonen <ka...@gmail.com>.
On Sat, Nov 21, 2009 at 3:31 AM, Thiago H. de Paula Figueiredo
<th...@gmail.com> wrote:
> Em Fri, 20 Nov 2009 19:41:46 -0200, Kalle Korhonen
> <ka...@gmail.com> escreveu:
>> Hmm... browsing the javadocs and source, I can see that *if* all of
>> the components would be using PageRenderLinkSource instead of the now
>> deprecated ComponentResources.createPageLink() it seems it would be
>> possible to override PageRenderLinkSource service to render absolute
>> links instead of relative links. It might break something else but it
>> sounds safe. Any committers reading this, what's your take - worth
>> creating an issue?
> You don't need to go that far. Just set the tapestry.force-absolute-uris
> configuration symbol to true in you AppModule.
Ah great, there's such a symbol! Nevertheless, you don't think that
the components should use PageRenderLinkSource for creating links?
Kalle
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: T5.1: Request forwarding breaks page/actionlinks
Posted by "Thiago H. de Paula Figueiredo" <th...@gmail.com>.
Em Fri, 20 Nov 2009 19:41:46 -0200, Kalle Korhonen
<ka...@gmail.com> escreveu:
> Hmm... browsing the javadocs and source, I can see that *if* all of
> the components would be using PageRenderLinkSource instead of the now
> deprecated ComponentResources.createPageLink() it seems it would be
> possible to override PageRenderLinkSource service to render absolute
> links instead of relative links. It might break something else but it
> sounds safe. Any committers reading this, what's your take - worth
> creating an issue?
You don't need to go that far. Just set the tapestry.force-absolute-uris
configuration symbol to true in you AppModule.
--
Thiago H. de Paula Figueiredo
Consultor, desenvolvedor e instrutor em Java, Tapestry e Hibernate
Coordenador e professor da Especialização em Engenharia de Software com
Ênfase em Java da Faculdade Pitágoras
http://www.arsmachina.com.br
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: T5.1: Request forwarding breaks page/actionlinks
Posted by Kalle Korhonen <ka...@gmail.com>.
Hmm... browsing the javadocs and source, I can see that *if* all of
the components would be using PageRenderLinkSource instead of the now
deprecated ComponentResources.createPageLink() it seems it would be
possible to override PageRenderLinkSource service to render absolute
links instead of relative links. It might break something else but it
sounds safe. Any committers reading this, what's your take - worth
creating an issue?
Kalle
On Fri, Nov 20, 2009 at 1:16 PM, Kalle Korhonen
<ka...@gmail.com> wrote:
> Rado, did you ever create an issue for this? You run into the same
> issue when a container processes your request through an error
> dispatcher (same as server-side forwards but for errors) as described
> at http://wiki.apache.org/tapestry/Tapestry5HowToUseTapestryForCustomErrorPages.
> Page and actionlinks on this custom error page are pointing to the
> wrong location because they are rendered as relative links. You most
> certainly *don't* want to redirect in this case as you want the user
> to see the url that resulted in 401, 404, etc. Creating custom
> versions of those components might be more or less ok for my use case,
> but in general, I'm starting to wonder if it would be better if
> Tapestry just rendered absolute links everywhere. Does anybody have
> any creative workarounds for this?
>
> Kalle
>
>
> On Wed, Jun 17, 2009 at 5:36 AM, immutability <de...@bielik.org> wrote:
>>
>> Thank you for the link pointing to the older discussion - I missed that one
>> during my searches. Funny how everyone was saying to create a JIRA for this
>> issue, but there doesn't seem to be any JIRA for this at the moment (open or
>> closed) other than the old one related to the ComponentEventException in
>> 5.0.x. I think I'll submit a new issue for this, just to see if it's
>> something that will be considered for future releases.
>>
>> Rado
>>
>>
>>
>> P.Stavrinides wrote:
>>>
>>> This is a topic that has been discussed before on the list... I don't
>>> disagree with you that there is a need to support server side redirects,
>>> this is the key portion of my argument in favour of supporting them:
>>>
>>> "The two types of redirects are distinctly different and equally
>>> important. RequestDipsatcher.forward() is the preferred redirection
>>> approach for many banking sites / payment gateways etc because redirection
>>> is performed at the server (so no need to use a session or querystring
>>> parameters). Furthermore, you always deal with the same request/response
>>> and have the ability to set attributes in the request which can be
>>> retrieved even after redirecting... for example a simple page refresh will
>>> update both redirect source and target (nice for a wizard type UI),
>>> whereas with a sendRedirect() a new request/response is generated each
>>> time. "
>>>
>>> See this old post for the full discussion:
>>> http://www.nabble.com/t5%3A-forwarding-in-index-tt22694515.html#a23073223
>>>
>>>> I was also wondering how does Tapestry handle a custom ExceptionReport
>>>> page?
>>>> In this case, it also seems to perform a server-side forward or redirect
>>>> (the URL of the original page remains displayed, while the custom
>>>> ExceptionReport page is shown). But in this case, PageLinks and
>>>> ActionLinks
>>>> work properly.
>>> Good question, you can dig through the source code to be certain, but at a
>>> guess I think Tapestry simply renders markup and doesn't use a server side
>>> redirect.
>>>
>>> Peter
>>>
>>> ----- Original Message -----
>>> From: "immutability" <de...@bielik.org>
>>> To: users@tapestry.apache.org
>>> Sent: Tuesday, 16 June, 2009 17:34:58 GMT +02:00 Athens, Beirut,
>>> Bucharest, Istanbul
>>> Subject: Re: T5.1: Request forwarding breaks page/actionlinks
>>>
>>>
>>> Thank you for your reply Peter. I ran across the JIRA you posted, but I
>>> feel
>>> it was a bit different from whay I'm seeking - the other guy was getting
>>> exceptions upon doing the forward. I agree there's not much use to do the
>>> forwarding when Tapestry already has excellent mechanism to perform
>>> redirection.
>>>
>>> But since both Tapestry-Acegi and Tapestry-Spring-Security are documenting
>>> the user of acegi.accessDenied.url property, I'm wondering if there's a
>>> way
>>> to make it work properly with Tapestry pages? I mean - if Acegi/Spring
>>> Security performs a server-side forward to redirect the user to the
>>> "Access
>>> Denied" page, then it would be nice to be able to use this with any
>>> Tapestry
>>> page. Otherwise the only way would be to create a page with no
>>> Page/ActionLinks - so you could just as well use a plain static HTML page
>>> for that. A Tapestry page with the standard webapp menu would be more
>>> user-friendly.
>>>
>>> I was also wondering how does Tapestry handle a custom ExceptionReport
>>> page?
>>> In this case, it also seems to perform a server-side forward or redirect
>>> (the URL of the original page remains displayed, while the custom
>>> ExceptionReport page is shown). But in this case, PageLinks and
>>> ActionLinks
>>> work properly.
>>>
>>> Rado
>>>
>>>
>>>
>>>
>>>
>>> Server side forwarding does not work in Tapestry, and it seems there are
>>> no
>>> plans to implement it: there was a jira once for it
>>> (https://issues.apache.org/jira/browse/TAP5-607?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel)
>>> but it was closed.
>>>
>>> regards,
>>> Peter
>>>
>>> --
>>> View this message in context:
>>> http://www.nabble.com/T5.1%3A-Request-forwarding-breaks-page-actionlinks-tp24040558p24055691.html
>>> Sent from the Tapestry - User mailing list archive at Nabble.com.
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
>>> For additional commands, e-mail: users-help@tapestry.apache.org
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
>>> For additional commands, e-mail: users-help@tapestry.apache.org
>>>
>>>
>>>
>>
>> --
>> View this message in context: http://www.nabble.com/T5.1%3A-Request-forwarding-breaks-page-actionlinks-tp24040558p24073841.html
>> Sent from the Tapestry - User mailing list archive at Nabble.com.
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
>> For additional commands, e-mail: users-help@tapestry.apache.org
>>
>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: T5.1: Request forwarding breaks page/actionlinks
Posted by Kalle Korhonen <ka...@gmail.com>.
Rado, did you ever create an issue for this? You run into the same
issue when a container processes your request through an error
dispatcher (same as server-side forwards but for errors) as described
at http://wiki.apache.org/tapestry/Tapestry5HowToUseTapestryForCustomErrorPages.
Page and actionlinks on this custom error page are pointing to the
wrong location because they are rendered as relative links. You most
certainly *don't* want to redirect in this case as you want the user
to see the url that resulted in 401, 404, etc. Creating custom
versions of those components might be more or less ok for my use case,
but in general, I'm starting to wonder if it would be better if
Tapestry just rendered absolute links everywhere. Does anybody have
any creative workarounds for this?
Kalle
On Wed, Jun 17, 2009 at 5:36 AM, immutability <de...@bielik.org> wrote:
>
> Thank you for the link pointing to the older discussion - I missed that one
> during my searches. Funny how everyone was saying to create a JIRA for this
> issue, but there doesn't seem to be any JIRA for this at the moment (open or
> closed) other than the old one related to the ComponentEventException in
> 5.0.x. I think I'll submit a new issue for this, just to see if it's
> something that will be considered for future releases.
>
> Rado
>
>
>
> P.Stavrinides wrote:
>>
>> This is a topic that has been discussed before on the list... I don't
>> disagree with you that there is a need to support server side redirects,
>> this is the key portion of my argument in favour of supporting them:
>>
>> "The two types of redirects are distinctly different and equally
>> important. RequestDipsatcher.forward() is the preferred redirection
>> approach for many banking sites / payment gateways etc because redirection
>> is performed at the server (so no need to use a session or querystring
>> parameters). Furthermore, you always deal with the same request/response
>> and have the ability to set attributes in the request which can be
>> retrieved even after redirecting... for example a simple page refresh will
>> update both redirect source and target (nice for a wizard type UI),
>> whereas with a sendRedirect() a new request/response is generated each
>> time. "
>>
>> See this old post for the full discussion:
>> http://www.nabble.com/t5%3A-forwarding-in-index-tt22694515.html#a23073223
>>
>>> I was also wondering how does Tapestry handle a custom ExceptionReport
>>> page?
>>> In this case, it also seems to perform a server-side forward or redirect
>>> (the URL of the original page remains displayed, while the custom
>>> ExceptionReport page is shown). But in this case, PageLinks and
>>> ActionLinks
>>> work properly.
>> Good question, you can dig through the source code to be certain, but at a
>> guess I think Tapestry simply renders markup and doesn't use a server side
>> redirect.
>>
>> Peter
>>
>> ----- Original Message -----
>> From: "immutability" <de...@bielik.org>
>> To: users@tapestry.apache.org
>> Sent: Tuesday, 16 June, 2009 17:34:58 GMT +02:00 Athens, Beirut,
>> Bucharest, Istanbul
>> Subject: Re: T5.1: Request forwarding breaks page/actionlinks
>>
>>
>> Thank you for your reply Peter. I ran across the JIRA you posted, but I
>> feel
>> it was a bit different from whay I'm seeking - the other guy was getting
>> exceptions upon doing the forward. I agree there's not much use to do the
>> forwarding when Tapestry already has excellent mechanism to perform
>> redirection.
>>
>> But since both Tapestry-Acegi and Tapestry-Spring-Security are documenting
>> the user of acegi.accessDenied.url property, I'm wondering if there's a
>> way
>> to make it work properly with Tapestry pages? I mean - if Acegi/Spring
>> Security performs a server-side forward to redirect the user to the
>> "Access
>> Denied" page, then it would be nice to be able to use this with any
>> Tapestry
>> page. Otherwise the only way would be to create a page with no
>> Page/ActionLinks - so you could just as well use a plain static HTML page
>> for that. A Tapestry page with the standard webapp menu would be more
>> user-friendly.
>>
>> I was also wondering how does Tapestry handle a custom ExceptionReport
>> page?
>> In this case, it also seems to perform a server-side forward or redirect
>> (the URL of the original page remains displayed, while the custom
>> ExceptionReport page is shown). But in this case, PageLinks and
>> ActionLinks
>> work properly.
>>
>> Rado
>>
>>
>>
>>
>>
>> Server side forwarding does not work in Tapestry, and it seems there are
>> no
>> plans to implement it: there was a jira once for it
>> (https://issues.apache.org/jira/browse/TAP5-607?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel)
>> but it was closed.
>>
>> regards,
>> Peter
>>
>> --
>> View this message in context:
>> http://www.nabble.com/T5.1%3A-Request-forwarding-breaks-page-actionlinks-tp24040558p24055691.html
>> Sent from the Tapestry - User mailing list archive at Nabble.com.
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
>> For additional commands, e-mail: users-help@tapestry.apache.org
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
>> For additional commands, e-mail: users-help@tapestry.apache.org
>>
>>
>>
>
> --
> View this message in context: http://www.nabble.com/T5.1%3A-Request-forwarding-breaks-page-actionlinks-tp24040558p24073841.html
> Sent from the Tapestry - User mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: users-help@tapestry.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: T5.1: Request forwarding breaks page/actionlinks
Posted by immutability <de...@bielik.org>.
Thank you for the link pointing to the older discussion - I missed that one
during my searches. Funny how everyone was saying to create a JIRA for this
issue, but there doesn't seem to be any JIRA for this at the moment (open or
closed) other than the old one related to the ComponentEventException in
5.0.x. I think I'll submit a new issue for this, just to see if it's
something that will be considered for future releases.
Rado
P.Stavrinides wrote:
>
> This is a topic that has been discussed before on the list... I don't
> disagree with you that there is a need to support server side redirects,
> this is the key portion of my argument in favour of supporting them:
>
> "The two types of redirects are distinctly different and equally
> important. RequestDipsatcher.forward() is the preferred redirection
> approach for many banking sites / payment gateways etc because redirection
> is performed at the server (so no need to use a session or querystring
> parameters). Furthermore, you always deal with the same request/response
> and have the ability to set attributes in the request which can be
> retrieved even after redirecting... for example a simple page refresh will
> update both redirect source and target (nice for a wizard type UI),
> whereas with a sendRedirect() a new request/response is generated each
> time. "
>
> See this old post for the full discussion:
> http://www.nabble.com/t5%3A-forwarding-in-index-tt22694515.html#a23073223
>
>> I was also wondering how does Tapestry handle a custom ExceptionReport
>> page?
>> In this case, it also seems to perform a server-side forward or redirect
>> (the URL of the original page remains displayed, while the custom
>> ExceptionReport page is shown). But in this case, PageLinks and
>> ActionLinks
>> work properly.
> Good question, you can dig through the source code to be certain, but at a
> guess I think Tapestry simply renders markup and doesn't use a server side
> redirect.
>
> Peter
>
> ----- Original Message -----
> From: "immutability" <de...@bielik.org>
> To: users@tapestry.apache.org
> Sent: Tuesday, 16 June, 2009 17:34:58 GMT +02:00 Athens, Beirut,
> Bucharest, Istanbul
> Subject: Re: T5.1: Request forwarding breaks page/actionlinks
>
>
> Thank you for your reply Peter. I ran across the JIRA you posted, but I
> feel
> it was a bit different from whay I'm seeking - the other guy was getting
> exceptions upon doing the forward. I agree there's not much use to do the
> forwarding when Tapestry already has excellent mechanism to perform
> redirection.
>
> But since both Tapestry-Acegi and Tapestry-Spring-Security are documenting
> the user of acegi.accessDenied.url property, I'm wondering if there's a
> way
> to make it work properly with Tapestry pages? I mean - if Acegi/Spring
> Security performs a server-side forward to redirect the user to the
> "Access
> Denied" page, then it would be nice to be able to use this with any
> Tapestry
> page. Otherwise the only way would be to create a page with no
> Page/ActionLinks - so you could just as well use a plain static HTML page
> for that. A Tapestry page with the standard webapp menu would be more
> user-friendly.
>
> I was also wondering how does Tapestry handle a custom ExceptionReport
> page?
> In this case, it also seems to perform a server-side forward or redirect
> (the URL of the original page remains displayed, while the custom
> ExceptionReport page is shown). But in this case, PageLinks and
> ActionLinks
> work properly.
>
> Rado
>
>
>
>
>
> Server side forwarding does not work in Tapestry, and it seems there are
> no
> plans to implement it: there was a jira once for it
> (https://issues.apache.org/jira/browse/TAP5-607?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel)
> but it was closed.
>
> regards,
> Peter
>
> --
> View this message in context:
> http://www.nabble.com/T5.1%3A-Request-forwarding-breaks-page-actionlinks-tp24040558p24055691.html
> Sent from the Tapestry - User mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: users-help@tapestry.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: users-help@tapestry.apache.org
>
>
>
--
View this message in context: http://www.nabble.com/T5.1%3A-Request-forwarding-breaks-page-actionlinks-tp24040558p24073841.html
Sent from the Tapestry - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: T5.1: Request forwarding breaks page/actionlinks
Posted by immutability <de...@bielik.org>.
Thank you for your reply Peter. I ran across the JIRA you posted, but I feel
it was a bit different from whay I'm seeking - the other guy was getting
exceptions upon doing the forward. I agree there's not much use to do the
forwarding when Tapestry already has excellent mechanism to perform
redirection.
But since both Tapestry-Acegi and Tapestry-Spring-Security are documenting
the user of acegi.accessDenied.url property, I'm wondering if there's a way
to make it work properly with Tapestry pages? I mean - if Acegi/Spring
Security performs a server-side forward to redirect the user to the "Access
Denied" page, then it would be nice to be able to use this with any Tapestry
page. Otherwise the only way would be to create a page with no
Page/ActionLinks - so you could just as well use a plain static HTML page
for that. A Tapestry page with the standard webapp menu would be more
user-friendly.
I was also wondering how does Tapestry handle a custom ExceptionReport page?
In this case, it also seems to perform a server-side forward or redirect
(the URL of the original page remains displayed, while the custom
ExceptionReport page is shown). But in this case, PageLinks and ActionLinks
work properly.
Rado
Server side forwarding does not work in Tapestry, and it seems there are no
plans to implement it: there was a jira once for it
(https://issues.apache.org/jira/browse/TAP5-607?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel)
but it was closed.
regards,
Peter
--
View this message in context: http://www.nabble.com/T5.1%3A-Request-forwarding-breaks-page-actionlinks-tp24040558p24055691.html
Sent from the Tapestry - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org