Hi,
Maybe you are caching web pages, either through explicit HTTP headers sent
from the web server to the client, invisible in the HTML code, or in the
Head section of your HTML pages, through the meta tags. If this is the
case, the token interceptor will probably return a valid response only the
first time the page is rendered, because a new token will not be computed,
but the old one will be resubmitted.
Andrei
repuken2 wrote:
Hi,
i'm having trouble with token interceptor, i'm using struts 2.1.8.1 with
eclipse and glassfish V3.
***we're using struts 1 plugin*** , we're migrating an old project wich
used struts 1 and so far everything is working ok, fileupload interceptor,
forms, etc. but toke-interceptor stuff. When goin from an action to
another that is protected-affected by this token-interceptor ( the jsp has
the s:token\ tag and the config.xml is properly configured having the
interceptor-ref token in the corresponding action) the interceptor indeed
works and interceps but it always return invalid.token result. The action
never executes as the application flow is interrupted at the interceptor
stage.
Has anybody experimented something similar? using struts 1 plugin or not?
does it have to do with this plugin and it would work using pure struts 2?
( don't ask me why but we need this up and working with the S1 plugin) ,
any ideas??
Cheerz and thanks in advance,
best regards.
Manuel
--
View this message in context:
http://old.nabble.com/struts-2-token-interceptor-problem-tp27714506p27742169.html
Sent from the Struts - User mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: user-unsubscr...@struts.apache.org
For additional commands, e-mail: user-h...@struts.apache.org