Downloadable viewMyClient results?

We sometimes use viewMyClient in troubleshooting user problems. Is there (or could there be) a way of obtaining the test results that is less error-prone than telling the client to "send us the page" (which might result in them sending us the link, or not copy-pasting everything, etc.)? Maybe a download link pointing to a data: URI, or encoding the results in whatever format into a querystring that support could decode?

I like both of your proposed implementations. Putting the results of the client test into query parameters of a special link would be the most efficient method. It would require client-side rendering of the results, which would, unfortunately, require a major refactoring of the page.

Your other solution, putting the result page into a data URI, is less elegant and may run into issues in some browsers that don't support very long URIs. However, it would require less development and it would be faster to implement. I've submitted a feature request with some sample code to the SSL Labs team.

My usual usecase is: we tighten TLS settings, and then somebody claims it doesn't work anymore, even though compat tables say it should for the browser they say they use. So, user agent plus the protocol features section would be the most important.

I like both of your proposed implementations. Putting the results of the client test into query parameters of a special link would be the most efficient method. It would require client-side rendering of the results, which would, unfortunately, require a major refactoring of the page.

Your other solution, putting the result page into a data URI, is less elegant and may run into issues in some browsers that don't support very long URIs. However, it would require less development and it would be faster to implement. I've submitted a feature request with some sample code to the SSL Labs team.

With the benefit of not thinking about this for a couple of days, even a "copy report to clipboard" button would be helpful, but I've not checked what the current state of JS clipboard API is w.r.t. the obvious security issues.