But that wouldn’t generate a 404 unless PHP is messing about somewhere. Unless you were getting the 404 with a GET request, it’s unclear if your current error is a 404 or not. (You got a 404 and switched to POST and now getting a different unspecified error, which means it’s your POST field encoding)
I did this and now it seems to be working. Maybe I shouldn’t have jumped the gun and made a post about it - I normally only do so as a last resort - but at least if others see it they might benefit from the answer.
–EDIT–
This was a temporary solution that I had when building on a localhost environment without HTTPS. Do not do the above in a live environment - instead make sure your SSL Certificate is up to date. Thanks to BarryCarlyon for the heads up.
Would this matter if I was only testing on a non https localhost? I’d assume once I moved this to my website that has an SSL I probably wouldn’t have had the issue no?
You should fix your localhost, otherwise localhost is not a good model of production.
And you’ll end up forgetting to remove your “localhost specific code” and break productions security, since the code you are adding introduces a security vulnerability
Thanks… I’ll bear this in mind… and I’ll also mark yours as the solution since mine is a temp workaround which could have negative repercussions for the average user.