After I tried to use GoDaddy to forward my old domain to my new domain using 301 redirect and test if t works, I found out that if you connect to the old domain for the first time after a while, it returns 302 found first with the same url! When you try it for the second time, it returns 301 redirect correctly. After noticing that, I just switched back to using my own server for redirection.
Here are the sample outputs of another domain that I have set to use 301 redirect in GoDaddy:
[[email protected] ~]# curl -i itfwy.com
HTTP/1.1 302 Found
Connection: close
Pragma: no-cache
cache-control: no-cache
Location: /
[[email protected] ~]# curl -i itfwy.com
HTTP/1.1 301 Moved Permanently
Cache-Control: max-age=900
Content-Type: text/html
Location: http://itdyn.com
Server: Microsoft-IIS/7.5
X-AspNet-Version: 4.0.30319
X-Powered-By: ASP.NET
Date: Fri, 01 May 2015 17:51:56 GMT
Content-Length: 0
Age: 1
Connection: keep-alive
[[email protected] ~]# curl -i itfwy.com/wp-admin
HTTP/1.1 302 Found
Connection: close
Pragma: no-cache
cache-control: no-cache
Location: /wp-admin
[[email protected] ~]# curl -i itfwy.com/wp-admin
HTTP/1.1 301 Moved Permanently
Cache-Control: max-age=900
Content-Type: text/html
Location: http://itdyn.com/wp-admin
Server: Microsoft-IIS/7.5
X-AspNet-Version: 4.0.30319
X-Powered-By: ASP.NET
Date: Fri, 01 May 2015 17:21:17 GMT
Content-Length: 0
Age: 1
Connection: keep-alive
[[email protected] ~]#
That’s very odd. It looks like a misconfigured reverse proxy. You can see in the instances where it does a 301 you have asp.net and IIS headers that are missing in the 302 responses. Those 302 responses must be some reverse proxy or load balancer.