This is what happens, totally randomly when a client is accessing a file. Let’s say you try to access the following URL: mysite.com/blog. These are the consecutive HTTP requests that will occur:
- GET mysite.com/blog
302 redirect mysite.com/AbCdE/blog - GET mysite.com/AbCdE/blog
302 redirect mysite.com/blog - GET mysite.com/blog
200 OK
Where AbCdE is always a random string made of 5 characters. That’s right, randomly, requests happen to be redirected twice through a random directory that doesn’t exist before the server finally delivers the resource. What’s the matter, you will say? Well, this has absolutely no reason to happen, and even if a visitor wouldn’t notice it by loading the URL in his browser, this can have an impact in other fields.
First, Google tends to index the temporary URLs that doesn’t exist, and this leads to undesired pages to be indexed. Secondly, as this is an unexpected behaviour, this can fuck your scripts in some situations. It especially happened to me, when apps that are connected to my website couldn’t manage redirections that don’t output more than 255 characters for example. Because of this unwanted random 302 redirect, I couldn’t guarantee the availability of my app anymore.
I am sorry, but I am not responsible, as a developer, for this, and I don’t have to adjust my code to my web hosting in this situation. It seems to be a recurring problem at GoDaddy’s, you can check it out on Google, many people are talking about it, and GoDaddy doesn’t seem to be fixing the issue…
But I really wonder where this bug (or feature) comes from. I bet maybe for a feature, where by differing the actual delivery of the resource, it’s freeing some load on the server when too many connections are coming in at the same time.
Anyways, I am now hosting my site on Namecheap.
Permalink
Permalink
I quitte godaddy a week ago for this reason. My website was on the 4GH shared plan
Permalink