Currently, unshared projects, when viewed, show a 404(/404).
This is wrong. 404 means not found. The server found the project, and decided not to allow the client to get it. this is a 403(/403) and should be displayed as such.
Projects that do not exist can have a 404.

EDIT: possibly give 401 Unauthorized when not logged in?

[url=redlink.com][color=red][u]red link[/u][/color][/url]

Well, I think it makes sense. You shouldn't be able to access unshared projects, after all.

But when they throw a 404, obviously something is wrong here. Maybe the project hasn't been created at all.

This would be better in bugs and glitches.

ResExsention wrote:

Well, I think it makes sense. You shouldn't be able to access unshared projects, after all.

But when they throw a 404, obviously something is wrong here. Maybe the project hasn't been created at all.

This would be better in bugs and glitches.

No.The user is suggesting to change the error sign for unshared projects to a 403. Look again at the OP.

space_elephant wrote:

Currently, unshared projects, when viewed, show a 404(/404).
This is wrong. 404 means not found. The server found the project, and decided not to allow the client to get it. this is a 403(/403) and should be displayed as such.
Projects that do not exist can have a 404.

Anyway, back to the suggestion.

Support, mainly because the reasoning behind these 2 errors aren't followed with the projects.
The 404 error was and is still meant for non-existent projects, studios, etc.
On the other hand, 403 errors are meant when the page the user is trying to view is restricted.

Epic_TV wrote:

ResExsention wrote:

Well, I think it makes sense. You shouldn't be able to access unshared projects, after all.

But when they throw a 404, obviously something is wrong here. Maybe the project hasn't been created at all.

This would be better in bugs and glitches.

No.The user is suggesting to change the error sign for unshared projects to a 403. Look again at the OP.

space_elephant wrote:

Currently, unshared projects, when viewed, show a 404(/404).
This is wrong. 404 means not found. The server found the project, and decided not to allow the client to get it. this is a 403(/403) and should be displayed as such.
Projects that do not exist can have a 404.

Anyway, back to the suggestion.

Support, mainly because the reasoning behind these 2 errors aren't followed with the projects.
The 404 error was and is still meant for non-existent projects, studios, etc.
On the other hand, 403 errors are meant when the page the user is trying to view is restricted.

Oh, sorry, thanks for clarifying.

Support, however I think a 401 error would make more sense, as unauthorized is more descriptive than forbidden

VFDan wrote:

Support, however I think a 401 error would make more sense, as unauthorized is more descriptive than forbidden

That one wouldn't work at all under the circumstances @space_elephant described. According to Google, “The 401 Unauthorized error is an HTTP status code that means the page you were trying to access cannot be loaded until you first log in with a valid user ID and password.”


And actually, I think I've found an error that may be better than 401 and 403.
423 Error: Locked (The resource that is being accessed is locked.)

If we can't decide on error code (403 is the standard for this sort of thing, so we'll just go with that instead of 423) we might as well use Error Code 418 “I'm a Teapot”

Error 418 "I'm a Teapot" wrote:

Any attempt to brew coffee with a teapot should result in the error code “418 I'm a teapot”. The resulting entity body MAY be short and stout.

When you go to an unshared project, it doesn't produce a 404 or a 403, instead, it just displays “Whoops! Our server is Scratch'ing its head”

I would support changing that message to “Sorry, this project is unshared”

Starstriker3000 wrote:

VFDan wrote:

Support, however I think a 401 error would make more sense, as unauthorized is more descriptive than forbidden

That one wouldn't work at all under the circumstances @space_elephant described. According to Google, “The 401 Unauthorized error is an HTTP status code that means the page you were trying to access cannot be loaded until you first log in with a valid user ID and password.”

That is what I'm talking about with the login. You have to log in with a valid user name and password, the one of the project creator.

wayyyy wrote:

When you go to an unshared project, it doesn't produce a 404 or a 403, instead, it just displays “Whoops! Our server is Scratch'ing its head”

It shows a “404” at the bottom of the page, actually.

Support. This makes total sense, but it is not urgent for the scratchteam to fix

Support. But … like …. it's not the biggest deal.