UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/50.0.2661.37 Safari/537.36

Example URL:
https://coop.ikrabbe-ask.de/

Steps to reproduce the problem:
1. Browse to a URL that supports only a limited set of ciphers (for example AES256-SHA256).
2. see ERR_CONNECTION_RESET
3. miss any information

What is the expected behavior?
it is ok for a client application to support only a limited subset of ciphers, but in the chaos of cipher names and possible key exchange, algorithm and hash combinations the user of the client software should be able to

1. See what exactly went wrong: The ERR_CONNECTION_RESET is just a common fallback for the "any error". Why the connection was reset? - Answer: The supported client side cipher list did not match with the list of ciphers the service porvides.

2. There should be an obvious way to get a list of supported cipher names. It should be quite simple to post this list on chrome://version AND `google-chrome --version`.

What went wrong?
The design of the client fails to report essential parameters how the client was built. Main builtin features are not visible to the user or at least the path to get this information is not obvious enough.

Did this work before? N/A 

Chrome version: 50.0.2661.37  Channel: n/a
OS Version: 
Flash Version: Shockwave Flash 21.0 r0