.Support for X-Failure header (leading to an alternative NZB)
Can any explain what this is, or provide a link?
"X-Failure Header" feature in 0.7.18
Forum rules
Help us help you:
Help us help you:
- Are you using the latest stable version of SABnzbd? Downloads page.
- Tell us what system you run SABnzbd on.
- Adhere to the forum rules.
- Do you experience problems during downloading?
Check your connection in Status and Interface settings window.
Use Test Server in Config > Servers.
We will probably ask you to do a test using only basic settings. - Do you experience problems during repair or unpacking?
Enable +Debug logging in the Status and Interface settings window and share the relevant parts of the log here using [ code ] sections.
"X-Failure Header" feature in 0.7.18
In the notes for 0.7.18 release it says"
Can any explain what this is, or provide a link?
Can any explain what this is, or provide a link?
Re: "X-Failure Header" feature in 0.7.18
It's mostly interesting for members of oznzb.com, they will announce their support soon.
More implementations may follow.
It allows indexers to send an alternative NZB automatically when the first one fails to complete successfully.
More implementations may follow.
It allows indexers to send an alternative NZB automatically when the first one fails to complete successfully.
Re: "X-Failure Header" feature in 0.7.18
It is also supported by dognzb.cr. Guide on setting it up here for those interested.
Re: "X-Failure Header" feature in 0.7.18
Is there any information about how X-Failure Header support can be integrated into a personal indexer I run.
Re: "X-Failure Header" feature in 0.7.18
If your indexer has the concept alternative NZB files,
you send a URL for the alternative NZB along with the first.
SABnzbd will call that URL when the original download fails to
get the next NZB.
you send a URL for the alternative NZB along with the first.
SABnzbd will call that URL when the original download fails to
get the next NZB.
Re: "X-Failure Header" feature in 0.7.18
I know what its supposed to do, what I wanted to know is there a API specification or something, can't be as simple as sending two NZB, they have to be linked somehow.shypike wrote:If your indexer has the concept alternative NZB files,
you send a URL for the alternative NZB along with the first.
SABnzbd will call that URL when the original download fails to
get the next NZB.
Using nzedb based indexer which is forked of nn+.
Re: "X-Failure Header" feature in 0.7.18
SABnzbd has no knowledge of how the server implements this (nor have I).
The only thing it does is use the url to get another file if a download fails.
All intelligence is on the server side.
The only thing it does is use the url to get another file if a download fails.
All intelligence is on the server side.
Re: "X-Failure Header" feature in 0.7.18
OK, thanks for the information.
I thought there was something code on the sabnzb side as it has to know which URL to fall back to if the first one fails.
I thought there was something code on the sabnzb side as it has to know which URL to fall back to if the first one fails.
Re: "X-Failure Header" feature in 0.7.18
The X-Failure header contains the URL for an alternative NZB file.
The header is already sent by the indexer when you retrieve the original NZB.
SABnzbd saves the URL and uses it when the download based on the original NZB fails.
The server may even have a chain of NZBs that can be offered in this way.
The header is already sent by the indexer when you retrieve the original NZB.
SABnzbd saves the URL and uses it when the download based on the original NZB fails.
The server may even have a chain of NZBs that can be offered in this way.