Fantia currently broken, requires header

[thatfuckingbird]

Started getting HTTP error code 422 on their /posts API endpoint.
Looks like they require an X-Requested-With header now with value "XMLHttpRequest".
As a workaround until this is added in the fantia extractor, the following config works:

        "fantia": {
            "headers":{
                "x-requested-with": "XMLHttpRequest"
            }
        } 

[appleshape]

I've added the headers to my config and I now get a 404:

$ .\gallery-dl.exe --cookies .\cookies.txt "https://fantia.jp/fanclubs/191767"
[fantia][error] HttpError: '404 Not Found' for 'https://fantia.jp/fanclubs/191767/posts'

Note that downloading a single post works fine:

$ .\gallery-dl.exe --cookies .\cookies.txt https://fantia.jp/posts/2017505
# .\gallery-dl\fantia\191767\2017505_thumb.jpg
# .\gallery-dl\fantia\191767\2017505_13465252.jpg
[fantia][warning] Unable to download 'uncatchable' files from https://fantia.jp/posts/2017505#post-content-id-3360150 // expected
[fantia][warning] Unable to download 'uncatchable' files from https://fantia.jp/posts/2017505#post-content-id-3360151 // expected

Details: Windows, 1.25.7.0, pre-built .exe from releases.

[thatfuckingbird]

I've added the headers to my config and I now get a 404:

$ .\gallery-dl.exe --cookies .\cookies.txt "https://fantia.jp/fanclubs/191767"
[fantia][error] HttpError: '404 Not Found' for 'https://fantia.jp/fanclubs/191767/posts'

Note that downloading a single post works fine:

$ .\gallery-dl.exe --cookies .\cookies.txt https://fantia.jp/posts/2017505
# .\gallery-dl\fantia\191767\2017505_thumb.jpg
# .\gallery-dl\fantia\191767\2017505_13465252.jpg
[fantia][warning] Unable to download 'uncatchable' files from https://fantia.jp/posts/2017505#post-content-id-3360150 // expected
[fantia][warning] Unable to download 'uncatchable' files from https://fantia.jp/posts/2017505#post-content-id-3360151 // expected

Details: Windows, 1.25.7.0, pre-built .exe from releases.

Ugh, you're right. With the header added, it returns 404. Without the header it works fine, but then the individual posts are broken... So it appears the header must only be set for the API endpoint, but not for the page listing posts.