-
-
Notifications
You must be signed in to change notification settings - Fork 4.7k
fix(capabilities): Expose if mod-rewrite is working via capabilities #44799
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
Conversation
|
/backport to stable29 |
Signed-off-by: Joas Schilling <[email protected]>
083140a to
bbaaaf4
Compare
Antreesy
left a comment
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.
LGTM
| 'webdav-root' => $this->config->getSystemValueString('webdav-root', 'remote.php/webdav'), | ||
| 'reference-api' => true, | ||
| 'reference-regex' => IURLGenerator::URL_REGEX_NO_MODIFIERS, | ||
| 'mod-rewrite-working' => $this->config->getSystemValueBool('htaccess.IgnoreFrontController') || getenv('front_controller_active') === 'true', |
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.
Looks like a copy-paste of
| 'modRewriteWorking' => $this->config->getSystemValue('htaccess.IgnoreFrontController', false) === true || getenv('front_controller_active') === 'true', |
Can we then use capabilities there to define modRewriteWorking in JSConfig?
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.
We could
modRewriteWorkingvia capabilities to allow pretty URL by clients #44798Currently only exposed on JS initial state for the webfrontend, not allowing clients to rely on it.
Checklist