> > However, with useRelativeRedirects="false" I see
> >
> > GET http://hostname/myapp?m=n=p
> > ==> 302: "http://hostname/login?a=b=d;
> >
> > The questions I have are 2: First, what happened with the trailing slash
> redirect. I vaguely remember discussions around it but I couldn't
> However, with useRelativeRedirects="false" I see
>
> GET http://hostname/myapp?m=n=p
> ==> 302: "http://hostname/login?a=b=d;
>
> The questions I have are 2: First, what happened with the trailing slash
> redirect. I vaguely remember discussions around it but I couldn't find
In Tomcat 7.0.67 with no "useRelativeRedirects" set on the context (which
defaults it to "true"), I see
GET http://hostname/myapp?m=n=p
==> 302: "login?a=b=d"
Now, this is expected behavior given the fix for [1]
[1] http://bz.apache.org/bugzilla/show_bug.cgi?id=56917
I reread
Hi,
Recent changes to Tomcat altered the behavior of our applications a bit so I've
got couple of questions. The versions in questions are 7.0.64 and 7.0.67. I am
aware of which is also described in the changelog for 7.0.67.
I have a filter acts on application "/myapp" that does a redirect in
Hi,
Recent changes to Tomcat altered the behavior of our applications a bit so I've
got couple of questions. The versions in questions are 7.0.64 and 7.0.67. I am
aware of which is also described in the changelog for 7.0.67.
I have a filter acts on application "/myapp" that does a redirect
On 08/02/2016 21:55, George Stanchev wrote:
>
>
> Hi,
>
> Recent changes to Tomcat altered the behavior of our applications a bit so
> I've got couple of questions. The versions in questions are 7.0.64 and
> 7.0.67. I am aware of which is also described in the changelog for 7.0.67.
There are
