Althttpd: View Ticket

Ticket Hash:	2ac5f38c1303ba441de210a7419c208c7ca31dcc
Title:	Wrong HTTP status codes?
Status:	Open	Type:	Code_Defect
Severity:	Cosmetic	Priority:	Low
Subsystem:		Resolution:	Open
Last Modified:	2022-01-07 20:09:13
Version Found In:
User Comments:
anonymous added on 2021-09-25 03:53:29: See: https://sqlite.org/althttpd/file?ci=tip&name=althttpd.c&ln=822 and the list of HTTP status codes here: https://www.iana.org/assignments/http-status-codes/http-status-codes.xhtml I think the RFC mentions that clients should only ever cares about the first 3 digits but it still bugs me :) P.S. Thanks for developing SQLite! anonymous added on 2021-09-25 04:00:29: See: https://sqlite.org/althttpd/file?ci=tip&name=althttpd.c&ln=821-829 and the list of HTTP status codes here: https://www.iana.org/assignments/http-status-codes/http-status-codes.xhtml These should be: "301 Permanent Redirect" => "301 Moved Permanently" "302 Temporary Redirect" => "302 Found" The correct status code for temporary redirect is 307 i.e. "307 Temporary Redirect". See: https://www.rfc-editor.org/rfc/rfc7231.html#section-6.4.7 I think the RFC mentions that clients should only ever cares about the first 3 digits but it still bugs me :) P.S. Thanks for developing SQLite! stephan added on 2022-01-07 20:09:13: FWIW, i think the change to 307 would be semantically incorrect. According to: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/307 "The only difference between 307 and 302 is that 307 guarantees that the method and the body will not be changed when the redirected request is made." IMO althttpd can make no such guaranty, but i'm willing to be taught otherwise.