SABConnect++ fails, but other apps using API work fine
Posted: April 2nd, 2017, 12:54 am
OK, I've been using SABNZBD Plus for ages, I have it running on my Mint Linux-based media server.Also for ages, I've been using SABConnect++, just fine. Recently, however, it stopped working. Sonarr, Headphones, Couch Potato all still work fine... I can also call the API directly, from my main PC (a Windows 10 box, not the same machine), both from LAN (using machine name) and through the external side (via my no-ip.org domain).
Tracing the SABConnect javascript call, it just fails on the XHTTPRequest() call, though the url and data (including my API key and credentials) look fine. I haven't played with it directly through javascript. This is in Chrome 59 (Canary build). Is it possible something changed in how chrome is handling ajax requests?
Just checking, and one of my own scripts (Through TamperMonkey) that makes use of ajax calls still works fine.
Has anybody else noticed this in Chrome 59? Does SABConnect++ need to be updated?
Tracing the SABConnect javascript call, it just fails on the XHTTPRequest() call, though the url and data (including my API key and credentials) look fine. I haven't played with it directly through javascript. This is in Chrome 59 (Canary build). Is it possible something changed in how chrome is handling ajax requests?
Just checking, and one of my own scripts (Through TamperMonkey) that makes use of ajax calls still works fine.
Has anybody else noticed this in Chrome 59? Does SABConnect++ need to be updated?