Skip to content
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

Nextcloud News: Connection error when trailing slash is missed while adding server #525

Open
DecaTec opened this issue Feb 5, 2023 · 2 comments · May be fixed by #620
Open

Nextcloud News: Connection error when trailing slash is missed while adding server #525

DecaTec opened this issue Feb 5, 2023 · 2 comments · May be fixed by #620

Comments

@DecaTec
Copy link

DecaTec commented Feb 5, 2023

Describe the bug
When connecting to Nextcloud News as source and the cloud domain is provided without trailing slash (e.g. https://cloud.domain.com), the connection cannot be established.

To Reproduce
Steps to reproduce the behavior:

  1. Add a server of type Nextcloud News API
  2. Provide a URL without trailing slash, e.h. https://cloud.domain.com

Expected behavior
Would be great when the trailing slash is not important when adding a Nextcloud News API server. The specific News API endpoint (https://cloud.domain.com/index.php/apps/news/api/v1-3) is also recognized by the program itself without the user has to provide a deep link.

Screenshots
image
German, it says: Error while connecting to the server. Please check the server configuration or your network status.

Platform (please complete the following information):

  • OS: Win 11
  • Version 1.1.3
@Alex9001
Copy link

Confirmed same issue on linux, git version.

other clients work without slash

thanks for this post I did not figure out why it was broken without you

quilicicf added a commit to quilicicf/fluent-reader that referenced this issue Nov 22, 2023
quilicicf added a commit to quilicicf/fluent-reader that referenced this issue Nov 22, 2023
@quilicicf
Copy link

Fix implemented in #620

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants