FR: Better network error reporting to reduce support headaches

When using network functions in JUCE there’s no useful error reporting.

You can’t tell the difference between a server not responding, an SSL configuration error, a DNS error or a rejected connection.

If WebInputStream::isError() and the various URL functions that also make connections (e.g. readEntireXmlStream), could be augmented by something that returned the most complete information available about the error codes from the operating system, many hours of support time could be saved!

2 Likes

Can I nudge this one again.

If you call downloadToFile in several cases you get nullptr if something fails but absolutely no information on WHAT FAILED! This is ok if you are working in a debugger, sure you can trace through the stuff and figure it out. But if it happens on a user machine …