Support 401 / 403 / etc. error codes about go-endpoints HOT 7 OPEN

Could do this with a custom error type:

type HTTPError struct {
  Err error
  StatusCode int
}

from go-endpoints.

But those are already defined in https://github.com/GoogleCloudPlatform/go-endpoints/blob/master/endpoints/errors.go

For instance, you could do return endpoints.UnauthorizedError if you wanted to respond with 401.

Or is it something else?

from go-endpoints.

DERP. My bad. I just ASSumed they weren't defined since endpoints.CurrentUser doesn't use them.

I suppose I should change the issue title to: Document custom errors and use 401 / 403 for relevant auth errors. WDYT?

from go-endpoints.

@dhermes yeah, I think it's a good idea! We should revise all returned errors. I think we were returning those generic errors because the pre-defined ones didn't exist at that point.

from go-endpoints.

We should remove the requirement that the Error messages begin by their equivalent StatusText... Right now if you create a new NotFound error, it will revert to a 400 unless it starts by "Not Found"... I'll post a pr later.

from go-endpoints.

Java 401 error implementation
OAuth Protecting a method https://cloud.google.com/appengine/docs/java/endpoints/getstarted/backend/code_walkthrough#oauth_protecting_a_method
Live demo https://apis-explorer.appspot.com/apis-explorer/?base=https://cloudendpointstic.appspot.com/_ah/api#p/tictactoe/v1/tictactoe.scores.insert Execute without OAuth

from go-endpoints.

There is a related issue already...

#110

Right if error message are not prefixed by the standard http status code's text then are turned into 400.

from go-endpoints.