Page 1 of 1

Empty NZB (double extension)

Posted: January 5th, 2014, 1:57 pm
by anorfidus
I've searched these forums so I apologize if this has been posted before but I'm trying to add an NZB to the queue via the api and addurl mode. I believe I have all of the correct syntax and when I simply put the NZB's url via Add NZB, it queues and downloads fine. However, when I use the addurl mode, I get an "OK" response yet the logging shows empty NZB with the following:

2014-01-05 12:50:09,088::WARNING::[nzbstuff:736] Empty NZB file a0c76697d7d2295f9815f761a5aecb42.nzb.nzb [https://www.smackdownonyou.com/getnzb/a ... aecb42.nzb]

I've checked all of my configs and I really don't know why the .nzb extension is being applied twice or if that's the issue. Here's the addURL api call I'm making (with my api key's modified)

[code]http://localhost:8080/api?mode=addurl&n ... y=xxxxxxxx[/code].

I've tried this api call with multiple different indexers that I know work so any help would be appreciated.

Thanks!

Re: Empty NZB (double extension)

Posted: January 5th, 2014, 2:27 pm
by shypike
Did you use proper HTML quoting?
Like replacing / with %2F etc.

Re: Empty NZB (double extension)

Posted: January 5th, 2014, 2:46 pm
by anorfidus
I did not as the API didn't indicate that the HTML quoting would be required. If it did require that, is there a reason it would still throw an OK response?

I'll try using the quoting. Thanks.

Re: Empty NZB (double extension)

Posted: January 6th, 2014, 2:42 pm
by shypike
The API is a bit dumb in this area.
OK means that the command has been read.
The problem is that there may be a very long time between the reception of the command
and the resulting NZB (or failure).
That's why the API call just returns "OK" if the number of parameters is OK.