Hi,
I agree with Rick last message, specially if you can only reproduce this
problem in PROD environment as said.
Just guessing but, sounds like some of your requests are going trough a
load balancer / reverse proxy in PROD (like nginx) and there is url rewrite
rule stripping down the parameters!
If the parameters are posted parameters are not being received by Stripes,
then something is hijacking the request before Stripes has a chance to
process them. If only 1 out of 10 requests fail, then you are try to find
the commonality where those requests fail.
My guess is that there is a defect
Hi Rémi,
Nothing in the log, stripes detecte the ActionBean URL, but with empty
parameter and excute the default handler.
Thanks
--
View this message in context:
http://stripes.996289.n3.nabble.com/Empty-requests-parameters-tp18061p18079.html
Sent from the stripes-users mailing list archive a
Hello,
Have you turned on logs ? Stripes can tell you everything it does, which
could help pinpoint the problem (binding/validation ? bean resolution ?
etc.).
HTH
Rémi
2017-07-19 13:00 GMT+02:00 MJ :
> Hello,
>
> Nothing special, a sample action bean like
>
> @UrlBinding(Bindings.LOGIN)
> publ
Hello,
Nothing special, a sample action bean like
@UrlBinding(Bindings.LOGIN)
public class LoginActionBean extends ActionBean {
@DefaultHandler
@HandlesEvent("connect")
public Resolution connect() throws Exception {
return new ForwardResolution(Resolutions.HOME);
}
}
I