It was actually a security fix we added back in Febuary.
You can read about ways to get around it here: