Hello! 👋
My NestJS is always sending 200 as Http...
# support-questions-legacyi
iruizmar
10/29/2022, 8:25 PMHello! 👋
My NestJS is always sending 200 as Http status code, even when failing (when invoking Supertokens endpoints). Is this the expected outcome?
r
rp_st
10/30/2022, 4:48 AMHey @iruizmar can you give me an example of when you are expecting it to return a non 200 and it’s returning a 200?
i
iruizmar
10/30/2022, 6:45 AMHey @rp_st! For example, on the OTP /consume method, if the OTP is invalid. Or if the deviceId/preAuthSessionId are wrong.
iruizmar
10/30/2022, 6:46 AMI would expect some 400 there.
r
rp_st
10/30/2022, 6:48 AMSo we differentiate between expected and unexpected errors. A 400 would happen if the request body is of a different structure than what the api expects. Vs the request body is of the right structure, but semantically something is wrong (for example the OTP is invalid)
rp_st
10/30/2022, 6:48 AMThis is done so that developers are forced to handle states like invalid OTP explicitly
i
iruizmar
10/30/2022, 7:02 AMOk! That sounds indeed opinionated. Makes sense. Thanks 🙂
r
rp_st
10/30/2022, 7:05 AMYup
10 Views