4 ms·

I hate to be this guy, but 410 seems a more appropriate code: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/410 https://developer.mozilla.org/en-US/d

by mstade 3y ago

I hate to be this guy, but 410 seems a more appropriate code: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/410 https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/410

quickthrower2 3y ago
Also the page actually returns 200, disappointingly.
hiAndrewQuinn 3y ago
Don't, I had no idea there was a dedicated status for that. I'm part of today's lucky 10,000 :D
devnine 3y ago
first thing I noticed also. I would suggest is a 417 Expectation failed. https://http.dog/417 https://http.dog/417
- teddyh 3y ago
  No, that would not be appropriate, since there is no “Expect” header you could send in the request to get a successful response. From RFC 9110, HTTP Semantics: The 417 (Expectation Failed) status code indicates that the expectation given in the request's Expect header field (Section 10.1.1) could not be met by at least one of the inbound servers. — <https://www.rfc-editor.org/rfc/rfc9110#name-417-expectation-failed https://www.rfc-editor.org/rfc/rfc9110#name-417-expectation-...>
xwowsersx 3y ago
> If you don't know whether this condition is temporary or permanent, a 404 status code should be used instead. Maybe they come back!
pavlov 3y ago
Someone could buy the flattr.com domain and then the site would be live again. IMO, "410 Gone" is only appropriate for URLs that contain unique identifiers because those are guaranteed to never be recycled.
kevincox 3y ago
I thought the same thing. You aren't the only one.
Zobat 3y ago
Kinda tempted to say 424 or 402 and you should always consider 418. Actually 418 might be appropriate as the service was clearly not built to solve the problem as it exists today. "The HTTP 418 I'm a teapot client error response code indicates that the server refuses to brew coffee because it is, permanently, a teapot."

4 ms·

I hate to be this guy, but 410 seems a more appropriate code: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/410 https://developer.mozilla.org/en-US/d

by mstade 3y ago

I hate to be this guy, but 410 seems a more appropriate code: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/410 https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/410

quickthrower2 3y ago
Also the page actually returns 200, disappointingly.
hiAndrewQuinn 3y ago
Don't, I had no idea there was a dedicated status for that. I'm part of today's lucky 10,000 :D
devnine 3y ago
first thing I noticed also. I would suggest is a 417 Expectation failed. https://http.dog/417 https://http.dog/417
- teddyh 3y ago
  No, that would not be appropriate, since there is no “Expect” header you could send in the request to get a successful response. From RFC 9110, HTTP Semantics: The 417 (Expectation Failed) status code indicates that the expectation given in the request's Expect header field (Section 10.1.1) could not be met by at least one of the inbound servers. — <https://www.rfc-editor.org/rfc/rfc9110#name-417-expectation-failed https://www.rfc-editor.org/rfc/rfc9110#name-417-expectation-...>
xwowsersx 3y ago
> If you don't know whether this condition is temporary or permanent, a 404 status code should be used instead. Maybe they come back!
pavlov 3y ago
Someone could buy the flattr.com domain and then the site would be live again. IMO, "410 Gone" is only appropriate for URLs that contain unique identifiers because those are guaranteed to never be recycled.
kevincox 3y ago
I thought the same thing. You aren't the only one.
Zobat 3y ago
Kinda tempted to say 424 or 402 and you should always consider 418. Actually 418 might be appropriate as the service was clearly not built to solve the problem as it exists today. "The HTTP 418 I'm a teapot client error response code indicates that the server refuses to brew coffee because it is, permanently, a teapot."