-
-
Notifications
You must be signed in to change notification settings - Fork 4.1k
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
X-Forwarded-Prefix not supported #12399
Comments
Is this Issue still valid? If not, please close this issue. Thanks! :) |
This issue has been automatically marked as stale because it has not had recent activity and seems to be missing some essential information. It will be closed if no further activity occurs. Thank you for your contributions. |
Has anything relating to |
In case it is helpful, someone compiled a list of feature requests / issues in other open source software: dotnet/aspnetcore#23263 (comment) |
cc @nextcloud/server-triage is this feasible? |
This issue has been automatically marked as stale because it has not had recent activity and seems to be missing some essential information. It will be closed if no further activity occurs. Thank you for your contributions. |
I understand it didn't get much activity. But what info is needed? I provided a workaround code snipped and there are a number of similar PRs in other projects. |
This issue has been automatically marked as stale because it has not had recent activity and seems to be missing some essential information. It will be closed if no further activity occurs. Thank you for your contributions. |
Could someone please remove the |
This issue has been automatically marked as stale because it has not had recent activity and seems to be missing some essential information. It will be closed if no further activity occurs. Thank you for your contributions. |
Steps to reproduce
PathPrefixStrip
)X-Forwarded-Prefix
headerExpected behaviour
Generated URLs should respect the prefix, e.g. add
/nextcloud
Actual behaviour
The provided prefix is ignored and assets use an URL without the prefix.
As a workaround the prefix can be added to the
overwritewebroot
config option.e.g.
The text was updated successfully, but these errors were encountered: