nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Does anybody know how to use ContextRedirectForwardAction?

ericzz

I want to use it in a controller to forward to subsequent page.

Find more posts tagged with

Comments

vpatel

Something like this:

ForwardAction faction = new ContextRedirectForwardAction("some/relative/url", false);

AlexC

to add to above:

Controller return type is a ForwardAction based object (or null if no redirect is needed). The ForwardAction object has 1 method called 'execute' which is given the HTTP request and response objects, so you can do whatever you need in there if you override the class (like generate custom response, redirect, etc).


ForwardAction myController(RequestContext context)
{
  // Do something if needed

  // Notify the flow that you would like a redirect
  return ContextRedirectForwardAction("/some/url.html", false);
}

ericzz

Thank you, guys. But I failed to forward to subsequent page by using ContextRedirectForwardAction (the default provided by interwoven).
I got 404 error.

I have a page A, in this page, one controller is used to submit a form and forward to next page B.
Here is my code: faction = new ContextRedirectForwardAction("app/session", false);
"app/session" is the url of page B, which i create it through sitemap --- > node ---> URL Aliases.

Do you know how can I debug or anaylsis this problem?

ericzz

Does anyone konw how to write the relative URL, if i want to forward from a.page to b.page?

vpatel

Does anyone konw how to write the relative URL, if i want to forward from a.page to b.page?

Usually $URL_PREFIX/sites/site-name/some/path/my.page tends to do it. That doesn't work for you?

ericzz

Usually $URL_PREFIX/sites/site-name/some/path/my.page tends to do it. That doesn't work for you?

It doesn't work. I got 404 error: HTTP 404 Not Found



// myController is included in a component on a.page
ForwardAction myController(RequestContext context)
{
  // Do something if needed

  // context redirect
  return ContextRedirectForwardAction("$URL_PREFIX/sites/appname/b.page", false);
}

vpatel

It doesn't work. I got 404 error: HTTP 404 Not Found



// myController is included in a component on a.page
ForwardAction myController(RequestContext context)
{
// Do something if needed

// context redirect
return ContextRedirectForwardAction("$URL_PREFIX/sites/appname/b.page", false);
}

Don't you need *new* in that return statement? Try with that. Also try URLRedirectForwardAction for redirects from one .page to another.

ericzz

Don't you need *new* in that return statement? Try with that. Also try URLRedirectForwardAction for redirects from one .page to another.

sorry, it did have "new". and I tried URLRedirectForwardAction, the redirect is working.
But I want to forward, so that i can keep the parameters in the request and pass them to next page, one of my bussiness logic need two pages have the same request. Like:


RequestDispatcher rd = context.getRequest().getRequestDispatcher("home.page");
rd.forward(context.getRequest(), context.getResponse());

vpatel

sorry, it did have "new". and I tried URLRedirectForwardAction, the redirect is working.
But I want to forward, so that i can keep the parameters in the request and pass them to next page, one of my bussiness logic need two pages have the same request. Like:
RequestDispatcher rd = context.getRequest().getRequestDispatcher("home.page");
rd.forward(context.getRequest(), context.getResponse());

Ok if you want to forward from one page to another in this case then you don't need the URL_PREFIX.

This works just fine for me: [color=#7f0055]new[/color] ContextRedirectForwardAction("/sites/site-name/some/path/my.page", [color=#7f0055]false[/color]);

If it is not working you then I would say increase your logging and use some additional tool to interrogate your request -- firefox has quite a few extensions that allow you to do some of that.

ericzz

Ok if you want to forward from one page to another in this case then you don't need the URL_PREFIX.

This works just fine for me: [color=#7f0055]new[/color] ContextRedirectForwardAction("/sites/site-name/some/path/my.page", [color=#7f0055]false[/color]);

If it is not working you then I would say increase your logging and use some additional tool to interrogate your request -- firefox has quite a few extensions that allow you to do some of that.

Thanks. I tried what you said


new ContextRedirectForwardAction("/sites/site-name/some/path/my.page", false);

There are some positive change. 404 error is gone, but the source code of "my.page" (the original xml format) is displayed in the browser, not the html output transformed by LiveSite.
My LiveSite Runtime is version 3.1, do you have any idea?

vpatel

There are some positive change. 404 error is gone, but the source code of "my.page" (the original xml format) is displayed in the browser, not the html output transformed by LiveSite.

Is happening on the TS Preview side or on the LS Runtime end?

ericzz

Is happening on the TS Preview side or on the LS Runtime end?

It happened on the LS Runtime.
As the TS Preview side, it seems the context url should be different, not "/sites/site-name/some/path/my.page", and I didn't find what it is after tried.

hyperlink.rptdesign

AlexC

There are some positive change. 404 error is gone, but the source code of "my.page" (the original xml format) is displayed in the browser, not the html output transformed by LiveSite.
My LiveSite Runtime is version 3.1, do you have any idea?

This seems to be a misconfigration or some custom change that is interfering with livesite. Have you made any custom filter/mapping changes? What is listening on port 80?

ericzz

This seems to be a misconfigration or some custom change that is interfering with livesite. Have you made any custom filter/mapping changes? What is listening on port 80?

I didn't make any custom filter, I checked the web.xml, there is only one default filter: runtime.filter.LiveSiteFilter.
I checked the log, it seems that it didn't go into LiveSiteFilter after forwarding.

anuj7700

Hi Eric,

We are facing the same issue where we get the .page file in plain text mode. Did you find a solution for this?

Please help

PaulW

Im getting this issue as well. Did anybody find a way to forward a request so the URL stays the same?

Rick Poulin

Did anybody find a way to forward a request so the URL stays the same?

Yup. Implement a standard Java servlet filter to rewrite the HttpServletRequest before it gets handed off to the LiveSiteRequestFilter. The cleaner but less supported way is to subclass+override the RuntimeRequestContext only on the runtime side via customer-runtime-resource-config.xml and override the implementation of getRequest(). That second one is trickier to get right without negative consequences, so ignore the suggestion if you don't know wtf I'm talking about Smiley Wink

Note that both of the above solutions require that your rewrite logic be computed *before* any livesite code gets executed. It isn't possible to internal forward to a .page after LiveSite has already decided which page it's going to render.

BTW, the ContextRewriteForwardRequest either ends up doing a HTTP302 (fullRedirect=true) or a requestDispatcher.forward() (fullRedirect=false). In the latter case, it goes back to your app container, so this can only be used to do an internal forward to resources natively understood by your container, like JSP and HTML.

PaulW

Are you saying that the filter would replace my controller? or it could execute after my controller as forwarded? The problem is i need to user values in the User Profile, which i dont think would be available within a filter.

Rick Poulin

Are you saying that the filter would replace my controller?
> In a manner of speaking, yes. Specifically, it would replace the forwarding part but nothing else (if it even does anything else).

or it could execute after my controller as forwarded?
> Nope. That's the part that can't be done.

The problem is i need to user values in the User Profile, which i dont think would be available within a filter.
> Your filter can be made ApplicationContext aware, which would grant you access to all your Spring beans. That means you can resolve the UserProfileService and get your profiles directly from it. The only drawback is that it bypasses any LiveSite abstractions, which might get complicated depending on how you've set them up, but in most cases this'll work just fine.

You can make your filter a bean fired through DelegatingProxyFilter, which means it's already executing within Spring and you could inject a reference to the UserProfileService bean. That's the ideal scenario. If you need to make your filter an old-school ServletFilter, then you can make it ApplicationContextAware to give it a reference to the ApplicationContext object.