are u sure the wireshark catch the right channel/device ? try with openssl to localhost to see if the connection is ssl or not
sth like: openssl s_client -connect host:port hth On Thu, Jan 10, 2013 at 5:24 PM, Thomas Broyer <t.bro...@gmail.com> wrote: > > > On Thursday, January 10, 2013 4:59:47 PM UTC+1, Mike wrote: >> >> I used wireshark to examine the packets. All the packet exchanges were >> TCP and the payloads were clearly readable. There was not handshake and >> no encrypted packets. >> > > I'd swear it worked OK for me (used tcmdump and wireshark); and if your > browser tells you it's over HTTPS (even with a weak certificate), then I > wouldn't contradict it. > > -- > You received this message because you are subscribed to the Google Groups > "Google Web Toolkit" group. > To view this discussion on the web visit > https://groups.google.com/d/msg/google-web-toolkit/-/lqut1PoPgIEJ. > > To post to this group, send email to google-web-toolkit@googlegroups.com. > To unsubscribe from this group, send email to > google-web-toolkit+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/google-web-toolkit?hl=en. > -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
