The Initium 端传媒 router fails to fetch full text article behind paywall

[mintyfrankie]

Routes

/theinitium/channel/:type?/:language?

Full routes

/theinitium/channel/latest/zh-hans

Related documentation

https://docs.rsshub.app/routes/new-media#duan-chuan-mei-zhuan-ti-lan-mu

What is expected?

With default ENV variable or personal variable like INITIUM_BEARER_TOKEN, the router should be able to fetch full-text article from the source.

What is actually happening?

Some articles failed to be fetched in full-text mode, showing for example :

Deployment information

Self-hosted

Deployment information (for self-hosted)

No response

Additional info

No relative logs found regarding this issue.

This is not a duplicated issue

• I have searched existing issues to ensure this bug has not already been reported

[github-actions]

Searching for maintainers:

• /theinitium/channel/:type?/:language?: @prnake

To maintainers: if you are not willing to be disturbed, list your username in scripts/workflow/test-issue/call-maintainer.js. In this way, your username will be wrapped in an inline code block when tagged so you will not be notified.

如果所有路由都无法匹配，issue 将会被自动关闭。如果 issue 和路由无关，请使用 NOROUTE 关键词，或者留下评论。我们会重新审核。
If all routes can not be found, the issue will be closed automatically. Please use NOROUTE for a route-irrelevant issue or leave a comment if it is a mistake.

[prnake]

Maybe the initium changed some api, I’ll check this later

[mintyfrankie]

Thanks! Happy to help if you need some more information to trace down the issue.

[shyrz]

The same issue. Please help to check.

[prnake]

I think it's a known issue that The Initium disables access to the full text behind paywall via a fake (or real) search engine bot UA started from August, which means only paid accounts can read the full text. And I tested the full text accessing via configured password or token from a paid account works fine now.

[mintyfrankie]

Hi @prnake,

Just want to give a quick update on the issue; withe either INITIUM_BEARER_TOKEN or env variables on login and password it seems to work fine now; however the INITIUM_IAP_RECEIPT doesn't work anymore.

I sniffed the iOS application and found that it uses a standard Authorization header, with its value as token xxxxx rather than Bearer xxxx. Maybe it can be interesting to update the script, as from my testings this authorization method can keep alive much longer than bearer token.

I'd be happy to contribute and raise a PR if you want to, or you can patch a quick fix right away.

[mintyfrankie]

Also:

I think it's a known issue that The Initium disables access to the full text behind paywall via a fake (or real) search engine bot UA started from August, which means only paid accounts can read the full text. And I tested the full text accessing via configured password or token from a paid account works fine now.

Perhaps then we don't need to fake a search bot anymore, as it cannot bypass the paywall. Can be interesting to do a cleanup on the script to streamline the logic.

[prnake]

Hi @prnake,

Just want to give a quick update on the issue; withe either INITIUM_BEARER_TOKEN or env variables on login and password it seems to work fine now; however the INITIUM_IAP_RECEIPT doesn't work anymore.

I sniffed the iOS application and found that it uses a standard Authorization header, with its value as token xxxxx rather than Bearer xxxx. Maybe it can be interesting to update the script, as from my testings this authorization method can keep alive much longer than bearer token.

I'd be happy to contribute and raise a PR if you want to, or you can patch a quick fix right away.

It’s great if you would like to PR for the IOS login method. And although the current fake UA is not working, it does not cause side effects, so I think it’s not necessary to replace it.

[lucky13820]

I'm using my email and password, but it still fails to fetch full text, it shows Response code 401 (UNAUTHORIZED). Any idea why it doesn't work?

[mintyfrankie]

@lucky13820 I believe that we still haven't fixed the router on this issue; I'd like to work on this if possible but unfortunately I don't have the subscription anymore.

[lucky13820]

I’m happy to share my credentials for you to work on his router. How should I give it to you?  Thanks,Ryan Yao在 2024年5月27日，上午1:40，minty_frankie ***@***.***> 写道： @lucky13820 I believe that we still haven't fixed the router on this issue; I'd like to work on this if possible but unfortunately I don't have the subscription anymore. —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: ***@***.***>

[mintyfrankie]

I’m happy to share my credentials for you to work on his router. How should I give it to you?  Thanks,Ryan Yao在 2024年5月27日，上午1:40，minty_frankie @.> 写道： @lucky13820 I believe that we still haven't fixed the router on this issue; I'd like to work on this if possible but unfortunately I don't have the subscription anymore. —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: @.>

That would be great! You can reach me at gentle.flame4249 at fastmail.com.