hayesmd

Thank you, I think I definitely need to read those, but I did find a solution for the problem. We just migrated from Linux to Windows (I know don’t remind me), but we were having a fight with Go Daddy’s new mod_security rules for Apache and we were losing. Here’s the code that fixed my rewrite:

<rule name="Host Directories Fix" stopProcessing="true">
                <match url="^(.*)[^/]$" />
                <conditions logicalGrouping="MatchAny">
                    <add input="{HTTP_HOST}" pattern="^YOURDOMAIN.com\.com$" />
                     <add input="{REQUEST_FILENAME}" matchType="IsDirectory" />
                 </conditions>
                <action type="Redirect" url="https://YOURDOMAIN.com/{R:0}/" redirectType="Permanent" />
            </rule>

I placed this rule last in my set of rules.

Alright, now I’m getting somewhere. I need to add the trailing ‘/’.

Next question, how do I do this on a windows host using web.config

Thank you, yes the above works as well if I remove the entire redirect_to query string.

I have other writers that have been complaining about not being able to login because everytime you click submit it takes you back to the login.

I need to find a way to remove the redirect_to query string OR figure out how to edit what is sent back when the user goes to https://dailystealsdaily.com/wp-admin

Nope, you are not alone. We are having this very same issue on all 8 of our WP installs within our hosting account with Go Daddy.

I’ve been going round and round as well. I hope they find a solution quick before we are forced to find a new provider which could have the same issues.

Thanks, WPyogi, I’ll take a look at them:

Right now moving isn’t much of an option. The performance of the sites are blowing away our sites that are on a different host. We also pay more for those 2 sites hosted elsewhere than we do for 8 sites hosted on Go Daddy. We’ve also used 2 other hosts previously and had issues with the sites staying online.

Anyone know of a way to monitor exactly what goes on behind the scenes when a post is saved/published?

My theory is that WP is doing something with the content of the post and possibly validating all the links OR testing the rendered HTML, something and the Go Daddy mod_security is reacting to what’s being done within the browser most likely through the admin-ajax.php file.

It does not occur on any other hosting provider that we’ve used. We recently purchased a WP site that worked fine until we transferred it to our Go Daddy hosting. We have 2 other WP sites on a separate host and they do not exhibit this problem either. Granted those 2 sites are 3.5 and our Go Daddy sites are 3.6.

We’ve actually copy/pasted the text of a post between the 2 spectate sites and hosts and the error only occurs on the Go Daddy hosted sites.

We already tried that. Didn’t resolve the issue. Go Daddy’s stance was the hosting account works and is sending pages. The error is within the code being sent. In this case it looks like an internal core file of WP.

They did at least admit that it is their new mod_security file that is kicking out the IP for 60 seconds after more than 10 redirects occur within so many seconds.

They also said the mod_security was upgraded recently due to the recent bot attacks that took place in Jun-Jul.

I would like to know this too. I am looking to create a page with all the posts from the current day.