I haven’t though to try using the loopback IP address… that would be a nice workaround.
As to SSL support, I know this will seem a distinction without a difference, but the API we built has no inherent restrictions on accessing insecure resources. Rather, it’s the host environment (macOS w/ ATS) that’s enforcing those restrictions. IIRC (and something to be careful of) Windows should access insecure resources without complaint.
For caching, it’s important to note that we use the OS’s networking APIs for XHR & Fetch. For example, on macOS, we use
NSURLSession, which has a cache by default. It’s supposed to respect your response headers, so you should be able to configure your endpoint to expire the cache more frequently. (Let us know if this doesn’t hold, though.)
Finally, for binary data, we do support this, but not via
Blobs yet. Instead, you have to use
Blob support is coming soon.