Whenever you are unsure, you can have a look at Laravel’s API documentation with the source code. The Redirector class defines a $status = 302 as default value. You can define the status code with the to() method: Route::get(‘foo’, function(){ return Redirect::to(‘/bar’, 301); });
Ok, so I assume that you’re already able to monitor your client/server traffic. What you want to do is set a breakpoint on the response then fiddle with it before sending it on to the client. Here are a couple of different ways to do that: Rules > Automatic Breakpoints > After Responses In the … Read more
Adding answer for versions of Angular >= 4.3 (including 15) with new HttpClient that replaces http In Angular versions 4.3 and later, the HttpClient module has been introduced, which is an improved version of the old Http module. It allows easier access to HTTP responses, including status code and headers. Here’s an example of how … Read more
Actually, the W3C recommends (RFC 2616 §10.4.4 403 Forbidden) doing the opposite. If someone attempts to access a resource, but is not properly authenticated, return 404 then, rather than 403 (Forbidden). This still solves the information disclosure issue. If the server does not wish to make this information available to the client, the status code … Read more
The gist of it is, just use 200. A little more generally: You should just send back the same status code for the CORS preflight OPTIONS request that you’d send back for any other OPTIONS request. The relevant specs don’t require or recommend anything more than that. What the specs say: The Fetch spec at … Read more
That’s exactly what a 503 is. 503 means that the server was relying on connecting some other service, which did not respond in time. Server Error 5xx Checked up on Wikipedia and the listing there seems to imply that a 504 would be the one I’m thinking of. Quite possibly the link over is outdated. … Read more
Did you consider status codes 502 and 504? 502 – The server while acting as a gateway or a proxy, received an invalid response from the upstream server it accessed in attempting to fulfill the request. 504 – The server, while acting as a gateway or proxy, did not receive a timely response from the … Read more
It could be 415 Unsupported Media Type according to this list: http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10.4.16. 3rd party edit From the current RFC9110 HTTP Semantics The 415 (Unsupported Media Type) status code indicates that the origin server is refusing to service the request because the content is in a format not supported by this method on the target resource. … Read more
To be consistent I would suggest 400 Bad Request now if your backend apps are capable of identifying when the client gets disconnected or if you reject or close the connection, probably you could return Nginx’ non-standard code 499 or 444. 499 Client Closed Request Used when the client has closed the request before the … Read more
The correct one is 303. I use it and haven’t found any compatibility problems with UAs newer than Netscape 4 (1998, released 17 years ago). If you use 302, you’re risking that UA will re-send POST to the new URL instead of switching to GET. Still, if you’re worried about HTTP/1.0 clients (which don’t support … Read more