Long overdue, RED now support HTTP over SSL and TLS, thanks to support in Thor, the underlying HTTP library.

For example, try Google.

At the moment, it treats HTTPS just like HTTP, but over time we'll add checks for certificate validity and other HTTPS-specific concerns.

As always, please report any concerns, either using the feedback button on the home page, or in REDbot's issues list.

REDbot now does a number of checks on Content-Disposition headers (RFC6266) and Link headers (RF5988) in responses. It also checks for a number of issues in RFC5987 encoding, where that's used.

Over the weekend REDbot got a fairly big upgrade; it now supports saving and sharing your results:

When you save your results, they're available at the resulting URL for at least 30 days. 

The new REDbot also allows showing results in HAR, a JSON format:

For example, see the HAR for amazon.com's home page. So, now you can not only get REDbot results in a JSON format (an often-requested feature), but you can also feed them into a HAR viewer such as this one to see how the requests were made. 

Behind the scenes, REDbot is using the 'id' parameter to reference stored results; by default, all results are stored for a short amount of time, so that you can view them in different formats without re-running the tests. Saving them just pushes out the date when they'll be deleted. Different formats can be requested using the 'format' parameter, either with 'id' (as REDbot does for the 'view HAR' link) or directly with the 'uri' parameter (which will re-request everything).

I still have a lot of tweaking to do with the UI; feedback appreciated (as always).

Thanks to @jeromerenard, REDbot now has command-line support:

 

RED now has a little 'feedback' widget on the right-hand side, courtesy of UserVoice. Please leave suggestions and ideas!