redirect() in controller fails for Tomcat

implemented a fix. Appears to work on local tomcat 5.5.28

Works on my local tomcat 5.0.27 as well! Thanks alot!

Maybe I was a little fast ...

I'm sure it was working, but now it doesn't any more!

I tried a war in 5.0.28, 5.5.23 and 6.0.10 and the redirect did not work.

I installed the latest snapshot and created a new application. Again, the redirect() did not work in Tomcat!

Can you try again locally?

I checked out latest from trunk and build Grails myself.

I wrote a shell script that

• deploys the Grails build
• creates a new Grails application
• creates a simple controller with two actions (actiona & actionb) where the one (actiona) redirects to the other (actionb)
• creates a war
• deploys it to a Tomcat webapps directory
• starts Tomcat
• accesses actiona via wget
• checks if a redirection to actionb happened

On all my Tomat versions on Windows & Linux, redirect() didn't work.

So I'm afraid you'll have to reopen this issue.

Doesn't work in Glassfish V2 Milestone 4 either. Couldn't get the application to run at all under Resin 3.1, but that seems to be an unrelated issue

I think the priority should be raised to "Blocker".

Not work for me on Tomcat 6.0.10 too.

Same here – apparently – I tried deploying to Jetty 6.1, and any actions that do redirects results in the browser just sitting there, churning along indefinitely without ever reaching the destination page/view/action.

Using a 0.5-SNAPSHOT from this morning.

defo fixed this time

I wished I could confirm this, but here I still don't see redirect() working with Tomcat ...

Can you please attache a test case. It works locally for me.

Ok, I just saw that while fiddling around to find the cause of this problem, I replaced the redirect() with chain() in my test script.

Using redirect(), it indeed works here for me, too!

But shouldn't chain() work as well? I mean, isn't redirect(action:'otheraction') and chain(action:'otheraction') basically the same, ignoring that chain() can also pass model data around?

They call different code, I'll look into chain too and fix it

Could someone else test on Jetty 6.1.1? Things are better than they were, however I'm still seeing some various problems that aren't making sense to me. Someone with more experience might be better apt to understand and correlate the issues.

OK - I think I see what's going on w/ jetty 6.1.1 now: it's as if both 'redirects()' and 'chains()' are just simply being ignored/discarded; instead what happens is the action will just do the default render gsp.

So:

  // UserController.groovy

   def home = {

      redirect( controller: 'site', action: 'list' )

   }

doesn't actually redirect to the list action of SiteController, what it does is attempt to render .../views/user/home.gsp

( of course when home.gsp doesn't exist, then I get a:

HTTP ERROR: 500

/WEB-INF/grails-app/views/user/home.jsp

Ok i've put in some new code that changes quite a few things, I haven't tested it against Jetty 6, but believe it will work, could you test again? Michael could you also re-test for you, it works on my local tomcat 5.5.28, on glassfish and jetty

Cheers
Graeme

Also note this should hopefully also correct the chain method

Works for me on local Tomcat 6.0.7 and production Tomcat 6.0.10

Both redirect() and chain() work on

Tomcat 5.0.28
Tomcat 5.5.23 (I always wonder where you get 5.5.28 from ...)
Tomcat 6.0.10

Using a snapshot downloaded one hour ago, I see no change in the behavior when deployed to jetty-6.1.1 .

redirect's and chain's are simply being ignored, and the default view is rendered for the action regardless.

Apologies - I accidentally tested using a war generated against yesterday's snapshot and not the most recent snapshot. Sorry for the noise.

It works!

Many, many sincere thanks to you Graeme - I can deploy!