BUG in wordpress 4.0

I upgraded 3 servers and all servers are doing it.

@auth1299 –

I would suggest that your sites/servers have other issues as I have successfully updated 25 sites across three hosting accounts; all headers are OK 200 so I don’t see it being a WP matter.

This is a topic I am not familiar with so would not know what to try next; perhaps others will chime in.

Everyone else who’s not auth1299 please start your own topic per the forum welcome.

https://www.ads-software.com/support/forum/how-to-and-troubleshooting#postform

Jumping on someone’s topic with “Me too!” doesn’t do anything for that person’s problem unless you are trying to help them.

Is anyone else finding that after upgrading to wordpress 4.0 that the headers show 301 permanently moved instead of http ok 200?

@auth1299 Can you provide us with actual links to illustrate the problem?

For example, my own WordPress site doesn’t do what you are describing.

$ curl -I https://my-site/link-to-a-post/on-my-site/
HTTP/1.1 200 OK
Date: Sun, 14 Sep 2014 11:16:56 GMT
Server: Apache/2.4.7 (Ubuntu)

I’m just getting 200 status codes. A 301 redirect is not a bad thing but if the canonical URL is being used then it should come up with 200.