Hello, Trečiadienis 22 Gegužė 2013 21:43:28 David Woodhouse rašė: > On Tue, 2013-05-21 at 08:55 +0300, Modestas Vainius wrote: > > Yeah, for example, openconnect still complains with error messages after > > XML POST even in non-verbose mode. > > Thanks. Please could you test the second patch I just committed to git, > on its own (i.e. without the previous patch, which I also committed). > I'd like to check that the "notice the connection broke, and make a new > one" code is working. > http://git.infradead.org/users/dwmw2/openconnect.git/commitdiff/fe85faaeecdd > 3da
Sure. It seems to work. # openconnect -v https://gwaddress.example.com/ POST https://gwaddress.example.com/ Attempting to connect to server xx.xx.xx.xx:443 SSL negotiation with gwaddress.example.com Connected to HTTPS on gwaddress.example.com Failed to read from SSL socket: A TLS packet with unexpected length was received. Error fetching HTTPS response GET https://gwaddress.example.com/ Failed to write to SSL socket: The specified session has been invalidated for some reason. SSL negotiation with gwaddress.example.com Connected to HTTPS on gwaddress.example.com Got HTTP response: HTTP/1.1 303 See Other Content-Type: text/html Content-Length: 0 Location: https://gwaddress.example.com:443/webvpn.html Set-Cookie: webvpncontext=00@webvpn; path=/ Connection: Keep-Alive HTTP body length: (0) GET https://gwaddress.example.com/webvpn.html Got HTTP response: HTTP/1.1 200 OK Cache-Control: max-age=0 Content-Type: text/html Set-Cookie: webvpn=; expires=Thu, 01 Jan 1970 22:00:00 GMT; path=/ Set-Cookie: webvpncontext=00@webvpn; path=/ X-Transcend-Version: 1 Content-Length: 473 Connection: close HTTP body length: (473) Please enter your username and password. USERNAME:
signature.asc
Description: This is a digitally signed message part.
