Just... Why?
999 Request Denied
21–30 of 74 posts
Re: 999 Request Denied
#22I’ve always used 418 for this kind of thing
I use 418 for “code should not have gotten here” type situations.
It's a weird enough and unique enough error that I pretty much know what is possibly up the moment I see it.
Re: 999 Request Denied
#23I am wondering if it might have been chosen as a joke... 999 is a homonym for the German "nein, nein, nein" (no, no, no), which is rather fitting for a "go away" status code.
Re: 999 Request Denied
#24The page explaining all the codes should make it clear that using status code 999 is a bad idea. One reason why it's bad is because it violates RFC 2616 (§6.1.1): The first digit of the Status-Code defines the class of response. The last two digits do not have any categorization role. There are 5 values for the first digit: - 1xx: Informational - Request received, continuing process - 2xx: Success - The action was su…
See, that would require knowing why they are rejecting you. Is it us? Is it you? Hell we don't know and couldn't be arsed to figure it out, so, just...Nein. Nein Nein Nein.
Re: 999 Request Denied
#25This is super unprofessional. 999 means nothing, therefore it cannot be acted upon, therefore it is totally useless. Best description which I can come up with is "I don't like you and I won't say why, because I don't like you". The expected client behavior is sending in return an empty http post request with wtf header and value "I feel this server is passive aggressive towards me."
Time to draft a pass-ag RFC
Re: 999 Request Denied
#26> 499 Please Spoof User Agent In A More Believeable Manner
Re: 999 Request Denied
#27I’ve always used 418 for this kind of thing
I think somebody also used it as a response when they detected the request to be a CSRF attack?
Re: 999 Request Denied
#28I’ve always used 418 for this kind of thing
For us lazy people: https://http.dev/418
Or its less informative but cuter cousin: https://http.cat/418
Re: 999 Request Denied
#29> When sending an HTTP GET or HEAD request to LinkedIn for a specific profile [...] > It will also be returned if there are too many HTTP requests in a single day. This is similar to the HTTP 429 Too Many Requests error message. Similar? That is excatly what 429 was made for, or not? This is weird or just lazy.
I’m assuming the logic is that LinkedIn uses 999 in combatting crawler bots so they don’t want to give reasons why the request is denied. That would help the bot overcome the restriction. e.g. it might be because you’ve sent too many requests but it also might be that your user agent is blocklisted.
Obviously it’s bad practise to do this but I don’t think it’s a mystery why they’d want their denial to be opaque. I’m also having trouble getting that worked up about it. If its OK to return 418 as a joke it’s probably fine to return 999 to suspected crawlers.
Re: 999 Request Denied
#30I am getting 999 even in a browser, what the fuck