-
Notifications
You must be signed in to change notification settings - Fork 189
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
Feed discovery does not work with relative URLs in links #1385
Comments
https://validator.w3.org/feed/check.cgi?url=https%3A%2F%2Fk47.cz%2Frss.xml even the self reference is broken. I'd just recommend alerting author of this issue. |
Yes, that was the other problem I hit; I have already contacted the author about that. However, this issue is not caused by the broken self-link in the feed. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. |
What does it mean “no recent activity”? Should I keep commenting that yes, this is still broken? |
It means that nobody has time or motivation to do something about it. So at some point it'll be closed automatically unless someone fixes it before then. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. |
When a feed is added using the feed discovery feature, and the feed link uses a relative URL, the discovery needs to resolve the URL relative to the provided website URL. Fixes nextcloud#1385
When a feed is added using the feed discovery feature, and the feed link uses a relative URL, the discovery needs to resolve the URL relative to the provided website URL. Fixes nextcloud#1385 Signed-off-by: Mormegil <[email protected]>
Solved here: alexdebril/feed-io#422 |
I made another PR fix, but it hasn't been approved yet: alexdebril/feed-io#431 |
Yea I saw that thanks, it seems like the maintenance activity on feed-io has gone down quite a bit, unfortunately... |
The same is true for absolute paths, for example on https://notapplicable.dev. |
Yeah, an “absolute path” ( [Also, note that this was (automatically) closed as either “stale” or “completed” [!], but it is very much not so, still the same problem as always, and “You do not have permissions to reopen this issue”, even though that would not help anyway, it would get closed automatically as stale again, I guess. Ceterum censeo https://nostalebots.xyz/ etc.] |
Well I have the power and despite there being an upstream PR, it is neither merged nor fixed in the News app itself. |
So regarding this issue unless someone here takes over the maintenance of feed-io I see no way to fix this. Taking over maintenance would mean to fork the repository, check all the open PRs and merge them if needed. Then to setup the release and publishing procedure because news would still want to pull this via composer and other projects probably too. I have been thinking about doing this myself but didn't have the motivation or time to do that. Being maintainer of a project does not mean that you have to do all stuff like coding but to respond to questions if possible and to review PRs and stuff. |
IMPORTANT
Read and tick the following checkbox after you have created the issue or place an x inside the brackets ;)
Explain the Problem
When trying to add a blog to the News reader, I was unable to do so, News repeatedly claims the hostname was not found.
The (first) problem I found is that during the discovery phase,
<link>
element’shref
attributes are used as written which does not work for relative URLs (allowed by the spec).Steps to Reproduce
Explain what you did to encounter the issue
The problem is the k47.cz page links to its feed using a relative URL
<link rel=alternate type=application/rss+xml href=rss.xml title="RSS zdroj">
which is then not resolved and News just attempts to fetch an “URL” ofhttp://rss.xml
.It might be argued this is an upstream bug; feed-io’s
Explorer
might resolve the relative URIs itself. Hard to tell, there is no specification of its expected behavior, AFAICT.I was able to fix the problem by resolving relative URLs after discovery:
Patch fixing the problem
System Information
Contents of nextcloud/data/nextcloud.log
The text was updated successfully, but these errors were encountered: