![]() (Supporting HTTP/1.1 pipelining might be a good idea, too. Other apps tend to use HTTP basic auth as a first step only, translating that into some kind of reusable token. I think including some kind of auth token in cookies or query string might be a good idea for more resilient requests. It seems like there's definitely some kind of browser bug here, but I'm not clear on the root cause. When this occurs, the nzbget UI gives up and stops refreshing.But status updates are also the most common. I've never seen it happen for other requests. This happens with simple status update requests.Seemingly randomly, Safari sometimes omits Authentication headers on requests to /jsonrpc.Ok, unfortunately the issue has returned and still occurs in the latest develop branch :( Hopefully it will for him too this commented on 12b6a26 5 hours ago I'll reach the other user and ask him to make another test with the current version. Using localhost or 127.0.0. just appears in commented on 12b6a26 10 hours ago Use the alias that you set for the linked container to resolve nzbget, this will allow Sonarr to talk to the nzbget container. (And the web inspector isn't super verbose about failed connections. No HTTP responses to those failed requests at all. Ensure that your device has the best internet connection.Check this out if you are trying to logging using 192.168.2.1 IP Address.efore logging in to NZBGet. I had compared the network traffic in the Safari and Chrome web inspectors, and nothing seemed particularly different about Safari's failed requests, which seemed to indicate that the issue was TCP or lower. If you need more data for a repro, I can try rolling back. (I'm guessing that the first ~8 connections worked fine – the browser's connections-per-host limit – and that things started failing when it started trying to reuse the zombie sockets that were left open.) The problem could always be resolved by refreshing the page. But after a few API requests or refreshes, all connections would start failing. Initial page load always worked correctly.Client is Safari 9.0 running on the latest OS X 10.11 beta 8 15A279b.no SSL enabled at the moment, just accessing via HTTP over LAN (to a LAN hostname, " ").It however did help another user having issues with Firefox on Windows, that's why I've committed the patch with a hope it helps someone else commented on 12b6a26 10 hours ago I have sent this patch before to a user having errors when connecting from Safari/Mac to nzbget running on NAS, but the patch unfortunately didn't fix the problem for him. Can you please post more details about your system - was nzbget running on Mac or on another device (when you had communication errors)? This totally fixes the issues with nzbget and Safari. Comments from commit commented on 12b6a26 12 hours ago
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |