This is fixed with glib-networking master (and the next release, which I think will be 2.29.17). The patch should apply easily to earlier glib- networking releases as well. (http://git.gnome.org/browse/glib- networking/commit/?id=4175fd4718bfd247420fe20af492c944edf9b598)
FWIW, it seems to me that this is a bug in the server-side TLS implementation; the SNI should not be included as part of the saved session (since it's presented as part of the ClientHello, not in one of the messages that gets skipped when resuming), and even if it is saved, the server ought to refuse to resume the session if the SNI saved in the session doesn't match the SNI requested in the ClientHello. But I don't know exactly what bit of software would be responsible for that on the server side of launchpad. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/823325 Title: 400 Bad Request on Launchpad subdomains To manage notifications about this bug go to: https://bugs.launchpad.net/launchpad/+bug/823325/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
