-
Notifications
You must be signed in to change notification settings - Fork 7.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
【UK Parliament】只能抓到3条内容,网页上单页15条 #17106
Comments
This comment has been minimized.
This comment has been minimized.
4 similar comments
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
Searching for maintainers:
If all routes can not be found, the issue will be closed automatically. Please use |
本地正常 http://localhost:1200/parliament.uk/commonslibrary/type/data-dashboard |
这三个路由 https://rsshub.app/parliament.uk/commonslibrary/type/research-briefing https://rsshub.app/parliament.uk/commonslibrary/type/data-dashboard https://rsshub.app/parliament.uk/lordslibrary/type/research-briefing 对应两个链接 实际的对应网页应该是这三个 https://commonslibrary.parliament.uk/type/data-dashboard/ https://commonslibrary.parliament.uk/type/research-briefing/ https://lordslibrary.parliament.uk/type/research-briefing/ 我用ttrss订阅,有个右键打开路由对应的网页,本来应该是打开上面三个,结果是后缀为type的这个网页。 另外 单页15个内容,只抓了三条,网页上应该只有样式的分别,不是历史内容和头版内容的分别,见图 |
路由地址
完整路由地址
相关文档
https://docs.rsshub.app/routes/government#uk-parliament
预期是什么?
能够抓取更多的内容,按照时间倒序排列
实际发生了什么?
1、只能抓3条,Commonlibrary 和 House of Lords Library 都是这样
2、路由对应页面错误,两院全部都是 https://commonslibrary.parliament.uk/type ,指向type 这个错误页面
路由的内容摘录如下
应该是https://commonslibrary.parliament.uk/type/data-dashboard/ , https://commonslibrary.parliament.uk/type/research-briefing/ 和 https://lordslibrary.parliament.uk/type/research-briefing/
部署
RSSHub 演示 (https://rsshub.app)
部署相关信息
No response
额外信息
麻烦 @AntiKnot 哥
在网页中,我通过查看源代码,发现对应每个超链接的结构如下,搜
<div class="l-box l-box--no-border card__text">
能搜到15个结果还有
The text was updated successfully, but these errors were encountered: