Support and Announcements for the Tech Java Web Application Platform (setup, configuration, bugs, feedback).
New Member
Posts: 28
Joined: Mon Jan 07, 2013 12:42 pm


Postby pauldev » Mon Jul 15, 2013 3:35 pm

In your security demos, they all use HTTP, not HTTPS...
I am working on getting lds account authenticaion working in https. It seems like an easy thing to do. Just add requires-channel="https"...

I have this tag <sec:intercept-url requires-channel="https" pattern="/spring_security_login" access="permitAll" />

The problem I see is an error returned:
Your login attempt was not successful, try again.
Reason: Authentication method not supported: GET

I can clearly see that the default login html is POST.
Any ideas?

New Member
Posts: 4
Joined: Mon Feb 06, 2012 4:59 pm


Postby knowltont » Wed Sep 18, 2013 9:33 pm

Sorry to have taken so long to reply on this thread.

Just to verify, are you saying that the login form itself is using POST, and that this is the error message response when you click the submit button? Can you verify that the behavior is not the same when the only change is leaving off the requires-channel attribute?

Can you point me to the source control repo where to find your project that is exhibiting this behavior?


New Member
Posts: 1
Joined: Fri Nov 11, 2016 3:19 am
Location: 9345 Cemetery Dr. Scarsdale


Postby jameswarner1 » Fri Nov 11, 2016 3:48 am

Such a nice debate but HTTPS means more secure web page open in browser compare of simply HTTP.

Return to “Java Web Project Support (Stack)”

Who is online

Users browsing this forum: No registered users