> The team constantly bikesheds over correct status codes and at least a few are used contrary to the HTTP spec