-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
Conversation
Can one of the admins verify this patch? |
1 similar comment
Can one of the admins verify this patch? |
@krombel What about the following concerns:
What about showing a page to the user instead, explaining it has been removed and why? |
or as per #1527 give some kind of page that says "Congratulations! You have synapse running!" |
So you would prefer to
|
Ideally, the oldwebclient URL would redirect to |
So some page that mixes matrix.to and the homepage of riot (for the rooms), correct? But: I do not know if it is good to introduce another site that would need updates from time to time. So I think it might be enough to have a page that just links to matrix.org and matrix.to instead of a page that contains those information |
No, just links to helpful pages, like the
Yes, definitely. |
somehow this introduced the bug that synapse tried to handle all URL's to be relative to STATIC_PREFIX so all endpoints got not handled any longer. This commit introduces a redirect to `/_matrix/static` where the homepage gets automatically served to circumvent this bug.
An interesting problem is that the spec actually says there needs to be a web client: https://matrix.org/docs/spec/client_server/r0.3.0.html#login-fallback It feels kinda weird to say in the spec that a small webapp has to be published. Instead, the spec should be updated to get rid of that in my opinion. |
related Spec-PR: matrix-org/matrix-spec-proposals#1105 |
synapse/static/index.html
Outdated
<p>For questions about synapse or matrix, please visit <br /> | ||
<a href="https://matrix.to/#/#synapse-community:matrix.org">#synapse-community:matrix.org</a> or | ||
<a href="https://matrix.to/#/#matrix:matrix.org">#matrix:matrix.org</a>.</p> | ||
<p>Welcome in the matrix-universe :)</p> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
s/in/to/
synapse/static/index.html
Outdated
<h1>Synapse is running</h1> | ||
<p>Congratulations!</p> | ||
<p>Your Synapse server is listening on this port and is ready for messages.</p> | ||
<p>To use this matrix-server you'll need a client to use this server - e.g. one of |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
seems duplicative, """to use this server you need a client to use this server"""
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This also removes the login fallback which is unrelated to the angular client.
So do I understand it right that the fallback should stay and the angular client be removed? |
Yep, fallback should definitely stay (whether the angular client should go or not seems to be a different debate). |
@dbkr I don't understand how this should end up then. Should the endpoint still exist but can return a page which is not a client, or no data at all? or should there always be a client, just not the angular client? |
@dbkr I do not really understand what the purpose of leaving the login client is. |
@krombel the login client is not part of the obsolete client aiui |
The "login client" isn't really a client at all, its just a web page that can be embedded in a client to do the login flows. This makes it possible to login with any client even if the server has some obscure custom login flows which few clients support. Without this fallback mechanism clients wouldn't be able to login to servers that require custom login flows that the client doesn't understand. |
Yep, what @t3chguy and @erikjohnston said. This looks better. This is becoming much less my area of expertise now, but other potential things which may or may not be worth worrying about:
|
When this setting is set to true we have a redirect from `/` to ´STATIC_PREFIX`. If set to false a call to / will return with "No Resource"
This will also solve # |
Is there anything that’s blocking this PR from being merged? I guess non-critical issues can be fixed incrementally in separate PRs. |
Just tuits to look at it properly. It's unlikely it will solve the captcha freedom issues, fwiw |
Why? The captcha is related to the webclient, if it’s removed, the recaptcha.js will also go away? |
@andrewshadura its probably used in the fallback login client |
Right, so if reCAPTCHA has to be used, can we dynamically load it and not ship the minified source instead? |
recaptcha is part of the spec: https://matrix.org/docs/spec/client_server/r0.3.0.html#google-recaptcha. Removing support from synapse will not fix that, which is the subject of #1561 aiui. (on the other hand, that makes it a spec issue, not a synapse issue: updated accordingly).
almost certainly. Definitely an orthogonal problem though, and the subject of #1932, aiui. |
This is largely a precursor for the removal of the bundled webclient. The idea is to present a page at / which reassures people that something is working, and to give them some links for next steps. The welcome page lives at `/_matrix/static/`, so is enabled alongside the other `static` resources (which, in practice, means the client API is enabled). We'll redirect to it from `/` if we have nothing better to display there. It would be nice to have a way to disable it (in the same way that you might disable the nginx welcome page), but I can't really think of a good way to do that without a load of ickiness. It's based on the work done by @krombel for #2601.
Thanks for finally handling it 😏 |
This got requested several times as in #1527
This introduces a homepage which is located at
/_matrix/static/
and redirects the old webclient-path (/_matrix/client
) to that path as well if the webclient is enabledWhy
/_matrix/static/
is used is described in the commit-description of ba0c18eThis would close #1527, #1883, #2113 and indirectly #1250 and #1353
Signed-Off-by: Matthias Kesler [email protected]