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

Documentation on reverse-proxy setup for the compatibility layer is not clear enough #1941

Open
matrixbot opened this issue Sep 10, 2024 · 0 comments
Labels
A-Configuration Related on what is configurable and how it can be configured A-Documentation Improvements or additions to documentation O-Frequent Affects or can be seen by most users regularly or impacts most users' first experience S-Tolerable Minor significance, cosmetic issues, low or no impact to users. T-Task Refactoring, removal, replacement, enabling or disabling functionality, other engineering tasks.

Comments

@matrixbot
Copy link
Collaborator

This issue was originally created by @sandhose at matrix-org/matrix-authentication-service#1941.

Users get confused about the compatibility endpoints which need to be routed to MAS using a reverse proxy.
This needs to be clarified in the documentation

Example #1835

@matrixbot matrixbot added A-Configuration Related on what is configurable and how it can be configured A-Documentation Improvements or additions to documentation O-Frequent Affects or can be seen by most users regularly or impacts most users' first experience S-Tolerable Minor significance, cosmetic issues, low or no impact to users. T-Task Refactoring, removal, replacement, enabling or disabling functionality, other engineering tasks. labels Sep 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-Configuration Related on what is configurable and how it can be configured A-Documentation Improvements or additions to documentation O-Frequent Affects or can be seen by most users regularly or impacts most users' first experience S-Tolerable Minor significance, cosmetic issues, low or no impact to users. T-Task Refactoring, removal, replacement, enabling or disabling functionality, other engineering tasks.
Projects
None yet
Development

No branches or pull requests

1 participant