google-cloud-endpoints

问题 My endpoint method generates a different response for each invocation regardless of the parameter list. I often see my client call the endpoint with the same parameter list, and the front end instance returns a cached response. In the official documentation I read that ApiMethod#cacheControl has been deprecated. On the other hand, the documentation says that the @Api-scopped annotation @ApiCacheControl has not been implemented yet so adding the following makes no difference. cacheControl =

问题 My endpoint method generates a different response for each invocation regardless of the parameter list. I often see my client call the endpoint with the same parameter list, and the front end instance returns a cached response. In the official documentation I read that ApiMethod#cacheControl has been deprecated. On the other hand, the documentation says that the @Api-scopped annotation @ApiCacheControl has not been implemented yet so adding the following makes no difference. cacheControl =

问题 My endpoint method generates a different response for each invocation regardless of the parameter list. I often see my client call the endpoint with the same parameter list, and the front end instance returns a cached response. In the official documentation I read that ApiMethod#cacheControl has been deprecated. On the other hand, the documentation says that the @Api-scopped annotation @ApiCacheControl has not been implemented yet so adding the following makes no difference. cacheControl =

问题 We have an HTML5 client accessing a Google Cloud Endpoints backend. We want to offer users a reasonable range of sign-in methods , e.g.: sign-in with an existing OpenID, or alternatively sign-up with an email and password. These seem like basic requirements to us! If there is a better alternative that does not restrict our audience, then we'd consider it. We're encountering two problems: (1) it seems the Endpoints service will only authenticate Google accounts, and (2) we don't know how to

问题 Right now my OpenAPI yaml looks like this: And my Access Token coming out of my JWT in raw format looks like this: The Google-Issuer and the JWT iss are the exact same, the JWT kid matches the key ids inside the link provided by the google-jwks_uri, and the google-audiences match the aud.So, really, I can't see why this wouldn't work, and yet when i call the api with the Bearer access token i receive a 401 and "Jwt issuer is not configured". 回答1: @BryceSoker I ran into a similar problem and

问题 I am using OAuth with my app-engine server. It's rather simple to do, simple add User as one of the parameters. But when I do I get the compile error Multiple entity parameters. there can only be a single entity parameter per method... @ApiMethod(path = "updateDocument", name = "updateDocument", httpMethod = ApiMethod.HttpMethod.POST) public void updateDocument(User user, MyDocument input){ ... } It works fine for the methods of the form public MyBean sayHiUser(@Named("name") String name,

问题 I am using OAuth with my app-engine server. It's rather simple to do, simple add User as one of the parameters. But when I do I get the compile error Multiple entity parameters. there can only be a single entity parameter per method... @ApiMethod(path = "updateDocument", name = "updateDocument", httpMethod = ApiMethod.HttpMethod.POST) public void updateDocument(User user, MyDocument input){ ... } It works fine for the methods of the form public MyBean sayHiUser(@Named("name") String name,

问题 I am trying to POST image to google cloud storage via multipart request using their JSON API, but I am receiving an error: "code": 400, "message": "Bucket is requester pays bucket but no user project provided." HERE IS MY REQUEST: POST /upload/storage/v1/b<my_bucket_here>/o? uploadType=multipart&name=testPostman HTTP/1.1 Host: www.googleapis.com Content-Length: 2139 Authorization: Bearer ya29.<my_token_here> Cache-Control: no-cache Postman-Token: 6fb40df7-3a0d-fda6-a94e-63365f594c9d Content

问题 We just migrated to google cloud endpoints v2 / java8 and found that latency has gone up. We see this kind of request in traces often: https://servicecontrol.googleapis.com/v1/services/<myapi>.endpoints.<myappid>.cloud.goog:check Which uses around 14ms. Also, somehow memory usage went up and our B2 frontends suddenly start blocking and having delays of 10s often, which could be a problem with connection pooling not done right, but was somehow not present with endpoints-v1 & java7 before. At

问题 For example, let's say user A needs to have GET permissions but no POST permissions to a certain endpoint. Is there any way to: Make roles where a certain user can't make certain types of requests to an endpoint? Make sure that endpoint follows those rules? 回答1: Regarding your first question, Cloud IAM roles are meant to control the access level of user accounts to the services and products that exist within your project. The IAM roles for Cloud Endpoints allow to restrict which users can