面试遇到让把 http code 三位数字拆开分别解释含义的

@joshua7v #16 随机应变了，基本不会反问，但是这个我是没忍住

什么煞笔问题.....

你看这个 1 他比 0 大一点 又比 2 小一点

这不 SEO 一波公司名？

@joshua7v 这事不同问题不同场合不同用词不同语气感受是不一样的，双方的感受可能也都不一样，抛回去可能分很多情况，质问，交流，请教都算抛回去，但是肯定是完全不同的反应。我的建议是看看自己是什么样的人，如果是会关注别人情绪或者被人拒绝了会不舒服那种，还想和别人说说，那就多一事不如少一事，相反如果认为双方都是陌生人，自己问了没什么，别人回不回答也没什么，也就是一点小事，过了就忘了，那就随便。

其实相当于一种谈判，多数情况下求职者处于劣势地位，谈崩了面试官大不了继续面试下一个，损失不大，因此可以更硬气，说什么“你回去自己查”之类的话。

400 和 500 是除出了错误又懒得解释具体原因时用的。

想听历史的话可以跟他介绍 451 的由来，源于 1953 年的反乌托邦小说《华氏 451 度》，纸的燃点 451 华氏度。

@AoEiuV020 有的 比如 429 限流

有意义吗？ wiki 上反正没说有
The first digit of the status code defines the class of response, while the last two digits do not have any classifying or categorization role.

你问问面试官 N 、M 、S 、L 每个字母都是啥意思

知道个常用 200 404 401 403 301 302 就足够了吧

面试官问得问题没啥毛病，这是基础知识。

这不是基础知识嘛，面试官没啥毛病

@Cu635 #31
@wellsc
所以每一位是什么意思？ 解释一下？

我他妈又不去应聘 IANA!
经典话术套路了,先整个一般人答不上来的问题,答不上来就贬低你,打压你,让你被动后在谈.

有寄吧用

跟面试官探讨一下 451

换个思路，面试官可能会用一个假的事例来测试你的反应能力，看你能不能（敢不敢）推翻他的定义

要我干脆一句话不知道

@Dvel #12 我想知道你这种说法的来源

rfc7231 压根没这说，就说了第一个数
https://datatracker.ietf.org/doc/html/rfc7231#page-47

Response Status Codes

The status-code element is a three-digit integer code giving the
result of the attempt to understand and satisfy the request.

HTTP status codes are extensible. HTTP clients are not required to
understand the meaning of all registered status codes, though such
understanding is obviously desirable. However, a client MUST
understand the class of any status code, as indicated by the first
digit, and treat an unrecognized status code as being equivalent to
the x00 status code of that class, with the exception that a
recipient MUST NOT cache a response with an unrecognized status code.

For example, if an unrecognized status code of 471 is received by a
client, the client can assume that there was something wrong with its
request and treat the response as if it had received a 400 (Bad
Request) status code. The response message will usually contain a
representation that explains the status.

The first digit of the status-code defines the class of response.
The last two digits do not have any categorization role. There are
five values for the first digit:

o 1xx (Informational): The request was received, continuing process

o 2xx (Successful): The request was successfully received,
understood, and accepted

o 3xx (Redirection): Further action needs to be taken in order to
complete the request

o 4xx (Client Error): The request contains bad syntax or cannot be
fulfilled

o 5xx (Server Error): The server failed to fulfill an apparently
valid request