@jbert said in HttpClient gives me 405s: I have seen this status code a lot where a POST to e.g. http://localhost/customers replies with a redirect to https://localhost/customers after which the client would fall back to sending a GET request (I can't remember if the HTTP spec states anything about this). Since that sample route is only ever used to create a new instance of a record, the server would then reply with a HTTP 405 status code once the GET request hits it. The HTTP client would only give the HTTP 405 code instead of the original HTTP 302. You're better off using 303 (if you want to switch to a GET) or 307 (if you want the method preserved). HTTP 302 - Wikipedia And yes, some frameworks are nasty in what they do here (and some browsers were awful in their misinterpretations).