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

Bugfix/update default plugins url #1141

Conversation

DominiqueComte
Copy link

The default plugins URL responds 2 chained permanent redirections, and it seems to be causing an issue when displaying the plugins page.
As they are permanent redirections, the ExtensionsManager might as well use the final value directly.

The error message I had was this, when displaying the plugins page:
Répertoire incorrect https://lms-community.github.io/lms-plugin-repository/extensions.xml - Timed out waiting for data

The URL in UNSUPPORTED_REPO is updated too, as it has the same 2x301 redirections.

The default plugins URL responds 2 chained 301 redirections, and it seems to be causing an issue when displaying the plugins page.
As they are permanent redirections, the ExtensionsManager might as well use the final value directly.

The error message I had was this:
Répertoire incorrect https://lms-community.github.io/lms-plugin-repository/extensions.xml - Timed out waiting for data
@michaelherger
Copy link
Member

Two re-directs shouldn't be a problem. If that is timing out, then there's a different issue. This is the first time I hear about this. What OS are you running LMS on?

I'd like to keep the two domains separate: the GitHub URL for technical, infrastructure URLs, Lyrion.org for user facing stuff. Just in case we'd have to split traffic at some point.

@DominiqueComte
Copy link
Author

LMS is running in a container on a Synology NAS, but it may have been a network security issue, I will re-check with the friend who's the one running it.

@michaelherger
Copy link
Member

Any news? Can we close this?

@DominiqueComte
Copy link
Author

Sorry, yes, it was a mistake in his network.

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 this pull request may close these issues.

2 participants