#Http error 418 solution code
Me: There's really no good HTTP status code for an XSRF violation, but it feels like it should be a class 4 code. While implementing this change, I was considering what HTTP status code to return in such a case. It is, for instance, sending a standard HttpWebRequest pointed at with the client's cookies/useragent forwarded, method set to POST and post values of the following:Ī while ago we finally switched the response to CSRF violations from a non-descript error page, as we had been doing for years, to something sensible that somewhat explains what's going on.
I will not dispute that this may be a result of my reverse proxy not doing something exactly the same as a browser, and because that is an OAuth authentication page and there may be some security or something, but perhaps it should be returning a more appropriate HTTP response?Īs requested, more information about the post request my client is sending. I would at first have thought "Bug", but it is obviously not, because, well - how would you end up with an HTTP server returning 418 without doing it on purpose. The pages I have found to return 418 with my reverse proxy are and Why would Stack Exchange ever be set up to return this status code? I was just playing around and everything was working perfectly, until I hit one page that suddenly returned HTTP error code 418 (I'm a teapot) which was an april fools joke from Hyper Text Coffee Pot Control Protocol. I recently wrote a reverse proxy which I have found to work wonderfully so far, and being an avid Stack Overflow user, I thought I would try it out there.
0 kommentar(er)
