You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Initially reported by: @nicerobot as #TRAC801
If the installation is occurring under a password protected directory and the .htaccess file isn't writable, installation will attempt to verify the rewrite rules by calling RemoteRequest to fetch /check_mod_rewrite but that will fail.
There is no indication that 401 is the error. The installer just keeps failing saying that the rules don't exist and .htaccess isn't writable.
Workaround is to make .htaccess writable during the installation.
Possible solution might be to add a rule to .htaccess to ignore protections for check_mod_rewrite, at least during installation.
The text was updated successfully, but these errors were encountered:
Author: @chrismeller
If the check_mod_rewrite call were made via AJAX, it would inherit the authentication you had to provide when originally loading the installer, would it not?
I don't know why it's being done via RemoteRequest, instead of as an AJAX call... I don't think that's how it originally was.
Initially reported by: @nicerobot as #TRAC801
If the installation is occurring under a password protected directory and the .htaccess file isn't writable, installation will attempt to verify the rewrite rules by calling RemoteRequest to fetch /check_mod_rewrite but that will fail.
There is no indication that 401 is the error. The installer just keeps failing saying that the rules don't exist and .htaccess isn't writable.
Workaround is to make .htaccess writable during the installation.
Possible solution might be to add a rule to .htaccess to ignore protections for check_mod_rewrite, at least during installation.
The text was updated successfully, but these errors were encountered: