Question: Is it safe to use the HTTP status code [308 Permanent Redirect](https://www.rfc-editor.org/rfc/rfc7238) ([suggestion](https://datatracker.ietf.org/doc/html/draft-reschke-http-status-308-07)) in server responses? The issue with 301 Moved Permanently is that it only works with GET requests (to be fair: POST will transform to GET which is NOT an option).

The status code is very newish in "RFC time" so what would you suggest?

What would a browser do if its not aware of 308? Would it find the location and do 302?

Answer: 
<https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/308>

The RFC 7538 proposal have wide support today. It's safe.

308 instead 301. 307 instead 302.

move != redirect

Move reminds a specific address and/or file moved. Redirect is a new location or address.
To end this: No it is not safe to use that status code. See comments for details.

> 
> 308 is not a standard - it's a proposal, still in the experimental stage. Browers should fall back to a 300 interpretation of any 301-399 error that they don't specifically understand.
> 
> 
> 

Some browsers just fail completely on that status code.