Rustorka: Unable to connect to indexer. Redirected to https://e.radikal.host/2023/05/17/vyur4654gffc434.jpg from indexer request

[soredake]

Is there an existing issue for this?

• I have searched the existing issues

Current Behavior

Unable to connect to indexer. Redirected to https://e.radikal.host/2023/05/17/vyur4654gffc434.jpg from indexer request

No such problem with Jackett.

Expected Behavior

This indexer should work.

Steps To Reproduce

1. Install prowlarr.
2. Create account on rustorka.
3. Try to configure indexer in prowlarr.
4. Unable to connect to indexer. Redirected to https://e.radikal.host/2023/05/17/vyur4654gffc434.jpg from indexer request

Environment

- OS: Ubuntu 22.04
- Prowlarr: 1.15.0.4361-ls62 by linuxserver.io
- Docker Install: Yes
- Using Reverse Proxy: No
- Browser: Firefox 124.0.1

What branch are you running?

Master

Trace Logs?

prowlarr.txt

[ilike2burnthing]

That's what the godbayadblock cookie should prevent,:

Indexers/definitions/v7/rustorka.yml

Lines 893 to 894 in 0b522f7

	headers:
	Cookie: ["godbayadblock=godbayadblock"]

Confirmed not working for Prowlarr, Docker and Windows.
Confirmed working for Jackett, Docker and Windows.

The xporn cookie for Zamunda.net also isn't working for Prowlarr, but is for Jackett:

Indexers/definitions/v7/zamundanet.yml

Lines 137 to 138 in 0b522f7

	headers:
	cookie: ["xporn=1"] # enable xxx downloads

Looks like a Prowlarr issue rather than specific to the indexers.

[mynameisbogdan]

I'm aware of the issue, and it's due to Prowlarr having Cookies and Headers as 2 separate fields while the definitions merges both into headers.

Until now I was aware that only eztv was affected by this.

Thanks for looking into it.