Backstage to prevent duplicate login verification, the front desk cope a bit, the result token has been bad use, very depressed .... Tangled
It turned out to be a problem with the form submission.
First of all:
1. Enter the first page will enter the interceptor, this will create tokens
public void intercept (Actioninvocation ai) {//create token, here is a value for the token to be entered into the page, and the Refresh page will change Ai.getcontroller (). creat Etoken ("Blogtoken"); Ai.invoke (); }
The page has a hidden field placed in this token with the "Note that this hidden field should be placed inside the form form"
Here at the front desk I use AJAX asynchronous commit, so with the data back to the value of the table is fastidious
data:$ (' #myform '). Serialize (),
MyForm is the ID value of my form. As for the username and password, as usual.
That's right!
The wrong question of Jfinal's token