News for hackers. Stuff that matters.

A comment on Some New HTTP Verbs. Parent comment

Re:Some New HTTP Verbs by themoonisachees on Tuesday September 13, 2022 @08:58AM (#32823650)
Http status codes barely do anything to begin with nowadays. I was bombarded with them in college, and if you look at any webapp, it only ever responds 200, 302 or 500.

Redirects are done in js, 404s are just normal pages, if that, and 401s are just not a thing on the public web anymore.

[ Parent | on HN ]
Re:Some New HTTP Verbs by quacksilver on Tuesday September 13, 2022 @09:00AM (#32823685)
I regularly see 401s and 403s on public APIs when interacting with them.

301s can be somewhat handy in certain circumstances too.

[ Parent | on HN ]
Re:Some New HTTP Verbs by capableweb on Tuesday September 13, 2022 @09:45AM (#32824214)
> Redirects are done in js

Redirects definitely happen in more places than you think/see, mostly because almost all tooling handle redirects transparently to the user, so you don't really notice it.

Doing redirects in JS is a huge waste of resources as well, as you'll need to load a full page with it's body (meaning the browser will parse and execute it) while having a 301 + Location header means the browser can redirect quicker without executing more stuff.

[ Parent | on HN ]
Re:Some New HTTP Verbs by delecti on Tuesday September 13, 2022 @09:21AM (#32823898)
I definitely use a bunch more than just those three, maybe as many as a dozen at various points. Probably another dozen occasionally leak through as problems from infrastructure we use. I could probably name several codes that I can't see much point in, but I'm sure people would respond why I'm wrong.
[ Parent | on HN ]