Your home address might be 123 Main Street, New York, NY 10001, and Facebook's address happens to be 66.220.144.0. When you visit a website, you are making a request to a web server.į,, /1525880/marthas-chocolate-chip-cookies, all of these sites have their own home address. It may be Chrome, Firefox, Safari or Internet Explorer.
Let's talk about how the HTTP protocol works.Īt its very foundation, the Internet is made up of two core things: clients and servers.Īny time you click on your browser, you are accessing the Internet through a web client. That's a 403 response.Ī 403 response might be used for known spammers, competitors, or maybe people from a certain country that have given you problems in the past. Your ID may or may not be fine, but you are forbidden from entering. That’s a 401 response.īut if I go to the bar, and the bouncer says "Wow, okay, we know who you are. You are forbidden."įor example, if I go to the bar and I have an unfamiliar ID or passport, the bouncer might say: “Hey, do you have a different ID actually? We can’t accept this one here. It may or may not have worked, but you can't come in. Can you try again?"Ī 403 response says "You tried logging in. The user entered an incorrect password, or the server doesn’t know who the user is, and is asking them to try and log in again.Ī 403 response is similar to a 401 response, with one explicit differenceĪ 401 response says "You tried logging in, but it didn't work. Usually, this means the user’s login credentials aren’t working.
Status code 403 – the “forbidden” error, is a client-side error.