Autodl irssi error downloading files ajax error parsererror

Connect and share knowledge within a single location that is structured and easy to search. When downloading a. My application requests a file from a server which is a proxy to fetch that file from another server. Note how "Content-Type" is preserved. The api server which is called is a Rails application and builds the request for the file resource using the parameters passed in:.

Which is using HTTParty. The GET request at the end of this post fetches only the file content. It does not fetch the file. So, the file content is sent back probably missing a necessary encoding step with MS files, thus throwing the at this point, perfectly legitimate parser error.

This is a shaky solution at best but it looks like the endpoints can agree on the content and mime types to present the file to the end user. We, unfortunately have no control over the end GET request and can only access file data as a BLOB and trust the encoding of the mime type is correct. How are we doing? Please help us improve Stack Overflow. Take our short survey. Stack Overflow for Teams — Collaborate and share knowledge with a private group.

Create a free Team What is Teams? Collectives on Stack Overflow. Learn more. Asked 6 years, 3 months ago. Active 6 years, 3 months ago. Viewed 1k times. This shouldn't be an update issue. That error is usually the result of irssi not running or multiple instances running.

Which then means ruTorrent can't connect to autodl-irssi properly. Sorry, something went wrong. Also anyone maintaining rutorrent add-on? I see changes made to free leech but its not updated in rutorrent plugin. They have always redirected as you see in the debug log. Nobody is currently maintaining the ruTorrent plugin. I do have a desire to add it to the autodl-irssi-community fold. It not only needs to be updated for new things we've added to autodl-irssi, it's layout desperately needs a redesign.

But until then, you will have to manually edit autodl. Skip to content. Star New issue. Jump to bottom. Update Issue.. Copy link. Update URL must have changed.