internet explorer 11 - Play 2.4 (Java) : posting a form returns Unauthorized in IE11, works in Chrome -


i migrated play 2.4.6 activator 1.3.7.

i have secured controller that's handling form. form submission works in chrome, in ie11, http post result 403 code (unauthorized). don't understand why happening. intermittent problem : same user connected, post works, doesn't. other posts application (on other page) work ok. can ?

i use action composition authorization , automatic csrf filters play provides, have worked under play 2.3. work play 2.4.6 in chrome, have followed steps of csrf configuration ... need make work in ie because of user base.

here controller :

@play.mvc.security.authenticated(secured.class) @authorize(minlevel=permissionlevel.vendor) public class soumrapideflexible extends controller { ...   public static result save(){           form<soumflex> boundform = soumflexform.bindfromrequest();      if(boundform.haserrors()){                   return badrequest(page.render(boundform));     }     ... // else stuff soumflex object   } } 

and here form, stripped down essential:

@(myform: form[soumflex]) @import helper._ <!doctype html> <html> <head>                                   <script data-main="@routes.assets.versioned("javascripts/main_soumflex")"  src="@routes.assets.versioned("lib/requirejs/require.js")"></script>               </head> <body>     @form(routes.soumrapideflexible.save(), 'class -> "form-horizontal") {         @csrf.formfield          <div class="form-group">             <label class="col-md-2 control-label" for="inputprojet">projet</label>             <div class="col-md-4">             <input type="text" class="form-control" id="inputprojet" name="inputprojet" placeholder="nom du projet" required>             </div>         </div>         //... , many other form fields in similar fashion...          <input type="submit" class="btn btn-primary" id="soumettresoum" value="save">                        </div> <!-- resumesoum -->     }    </div>                                </body> </html> 

it if user credentials lost or csrf token not right... has idea why i'd have such behavior in ie11? please help.

first used this implementation of global csrf filter gave me problem outlined above.

then tried this implementation (replacing gzip csrf) , problem seems have disappeared ! think having final property did trick.


Comments

Popular posts from this blog

authentication - Mongodb revoke acccess to connect test database -

r - Update two sets of radiobuttons reactively - shiny -

ios - Realm over CoreData should I use NSFetchedResultController or a Dictionary? -