-
Notifications
You must be signed in to change notification settings - Fork 44
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
[Bug] SSL Redirect Leading to "Too Many Redirects" Error #609
Comments
Thanks for reporting your issue. The fact that the is_ssl() function returns false, means that the detection occurrence if this didn't result in the corresponding fix. Normally, when is_ssl() returns false, Really Simple SSL will detect this, and add the following line to your wp-config.php:
You will see that if you do this, is_ssl() will return true, and all redirect issues are fixed. So the fix in this case should be to investigate why the plugin didn't add this in the first place. The first thing that comes to mind is maybe you had the wp-config.php set to not writable? The plugin should show a notice about it, but on multisite this might be less visible. |
Thanks for your reply. |
Adding the source sounds like a good idea. The notice should appear before SSL is activated within the plugin, so should be visible. I'll run some tests with this: the purpose of the plugin is to make such debugging unnecessary! |
I encountered a "Too Many Redirects" error while adding a new domain to my WordPress multisite network. After extensive debugging, I identified that the wp_redirect_to_ssl() function in the Really Simple SSL plugin was causing the issue. It seems like the is_ssl() functionwas returning false although SSL was actually already set up.
Steps to Reproduce:
Expected Behavior:
The new domain should be accessible without redirect errors.
Actual Behavior:
The new domain results in a "Too Many Redirects" error.
Workaround:
Suggested Improvement:
To facilitate easier debugging for others who might encounter this issue, I suggest adding an $x_redirect_by header attribute to the wp_redirect_to_ssl() function. This addition would provide clearer insight into the source of the redirects.
The text was updated successfully, but these errors were encountered: