https://bugs.kde.org/show_bug.cgi?id=395157
--- Comment #19 from emele...@gmail.com --- Created attachment 116737 --> https://bugs.kde.org/attachment.cgi?id=116737&action=edit New patch, check form >From vpn/openconnect/README: The auth-dialog handles the arbitrary forms as the server presents them, and spits out the cookie after a successful authentication. It's just a really simple web-browser, effectively. This is why reconnections are needed: the auth-dialog fills in the forms with the stored information, reconnects the server and receives the next form. The the process is repeated until there is no more information available, so that the user can fill in the rest if the connection is still not successful. So the key to solve this issue in a more general way would be to check the form and block the reconnection if the form has not changed. This is what I have done in the attached patch, and it apparently works (at least works for me). Now I'd appreciate someone checking the code (I'm not a great programmer), and testing it with other openconnect servers. y own testing is successful, but I don't have a real server to test on. I guess there are other possibilities to get this done, but I think the idea is correct. -- You are receiving this mail because: You are watching all bug changes.
