Boy do I feel like a dumb-ass :( , this is the second time I've been bit by getScreenTemplate().
I was using $link.setPage($data.ScreenTemplate), which returns the screen template as "foo/bar" not "foo,bar". I switched it to $link.setPage($data.Parameters.Template) and it worked fine. p.s. I apologize for not posting the EXACT code in my initial post. Thanks, Scott -----Original Message----- From: Weaver, Scott [mailto:[EMAIL PROTECTED]] Sent: Friday, January 04, 2002 1:23 PM To: 'Turbine Users List' Subject: RE: Comma in $link.setPage("foo,bar.vm") causes HTTP 400 Bad Requ est in Tomcat 4.0.1 per my TR.props tool.request.link=org.apache.turbine.util.template.TemplateLink This is the correct tool (opposed to TemplateLinkWithSlash ), is it not? You are correct, %2F is the slash (ref: http://i-technica.com/whitestuff/urlencodechart.html). I'm using 2.2b1 HEAD from 12/10/2001. I'll check the source and see if there is an issue. Scott -----Original Message----- From: John McNally [mailto:[EMAIL PROTECTED]] Sent: Friday, January 04, 2002 12:05 PM To: Turbine Users List Subject: Re: Comma in $link.setPage("foo,bar.vm") causes HTTP 400 Bad Request in Tomcat 4.0.1 I believe comma is %2C and %2F is / (slash). If you are really getting %2F it would cause problems which is the reason for using comma. Are you using a stock link tool? Which one? john mcnally "Weaver, Scott" wrote: > > Using Turbine 2.2b1 > > If I use this in the post action of my form I get a HTTP 400 Bad Request > from Tomcat: > > <form action="$link.setAction("my.action").setPage("foo,bar.vm")" > method="post"> > > which renders to: > > <form > action="http://localhost:8080/app/action/my.action/template/foo%2Fbar.vm"; > method="post"> > > As soon as I remove setPage("foo,bar") or change it to another top-level > template, setPage("foo"), everything works fine. > > I think it has something to do with the %2F (comma). > > My work around is just to: > > <input type="hidden" name="template" value="foo,bar"> > > This is probably more of a Tomcat issue, but I thought I would bring to the > group's attention and see if anybody had experienced it and may have a > different solution. > > Scott > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
