I have uploaded a new version on Google App Engine and have made it the default serving version. I have also deleted all older versions, but still GAE serves the older version on htttp connection while it serves newer on https connection. How to rectify it?
Related
I'm getting a 404 error when trying to access an API in a non-default app engine deployment.
I have a deployed Cloud Endpoint (first version and not Cloud Framework) service with an app engine version of 1 and API version of 1. This is successfully deployed and accessible as the default version - http://{project-id}.appspot.com/_ah/api/{name}/v1/{relative-path}.
I also have a second deployment using Cloud Framework with an app engine version of 2 and API version of 2. I did this by first generating and deploying an API config file with the hostname {project-id}.appspot.com. I then deployed the new service under a version 2. Checking the AppEngine UI console shows the two different versions deployed with v1 as the default version serving all traffic.
The problem though is I cannot access an API on the 2nd version. When I try accessing an API method with the URL http://2-dot-{project-id}.appspot.com/_ah/api/{name}/v2/{relative-path}, I get a 404 error. I don't see any entries in the Log viewer for that request. However when I access the root path, http://2-dot-{project-id}.appspot.com, I also get a 404 but do see an entry in the Log viewer.
When I make v2 the default version by migrating all traffic to it, I can then access all APIs on the 2nd version via the URL http://{project-id}.appspot.com/_ah/api/{name}/v2/{relative-path}. I don't know why I can't access these APIs when it's the non-default version.
Am I accessing the v2 deployment the wrong way when it's the non-default version? I don't think so because when I make it the default the APIs work. Is it rather something to do with how I deployed the API spec for version 2? Does it for some reason not apply to a non-default 2-{project-id}.appspot.com request.
Recently I've found out App Engine 1.9.1 has a bug which however does not occur in version 1.8.9 and below. I am developing my applications with Eclipse and the Google Plugin for Eclipse. In the Google properties of the project I switched back to 1.8.9. If I work locally I can see that it is using version 1.8.9 (the bug does not occur) however when I deploy to App Engine no matter what I do it will still run on 1.9.1. I even tryed to create a new project/application from scratch, still 1.9.1. I even deleted SDKs 1.9.1 and 1.9.0 from my system but nothing seems to help. What can I do? Thanks.
You don't control the version in production. It runs on Google servers and isn't deployed as part of your app.
Welcome to the cloud world where some parameters slip from your hand no matter how hard you try...
Indeed, you have no control over the AppEngine version that will be used to run your application in production. In fact, if you look carefully in the list of instance on your cloud console, you will see sometimes that some instances use an AppEngine version that is not even publicly available at the moment.
I 'm building an AppEngine application that stores data in Google Cloud Storage. I use the Google Cloud Storage Client (GCS) library as suggested.
My app is working when deployed on AppEngine (reading/writing/listing objects) but I cannot make it work on the development server. The development server keeps returning error 404 and GCS raises NotFoundError. The dev-appserver is supposed to emulate the cloud storage functionality without any specific configurations etc. I see in the log files that the dev server is accepting requests at "/_ah/gcs" yet it seems that there is no handler for that url. I 've tried with version 1.8.5 and 1.8.6. Apart from my app, not even the demo app provided by Google works.
Is there something that I 'm missing here, e.g. a special configuration for the dev-appserver?
Sorry the following change was pushed out too early by mistake. It only works with 1.8.8 SDK. We are streamlining the release process of gcs client to align with SDK. Sorry
https://code.google.com/p/appengine-gcs-client/source/detail?r=125
Without this change, it works on 1.8.7 SDK.
From the observations I have seen from our application App Engine only provides the endpoints from the version which is set as default. When we deploy a new version including a new endpoint it's not available for clients when using Traffic Splitting.
You can deploy your application in two steps.
Deploy a new version including the new endpoint not used by any client and set this version to default.
Deploy a new version and setup traffic splitting for you application.
I have developed a GAE application on version 1.5.0 of the SDK. It is already deployed to http://linkpad.me and working properly (as of this writing). I am wondering how the upgrade process should go to get to version 1.5.1 of the GAE SDK.
As far as I can tell, I should do the following:
Download version 1.5.1 of the SDK
Test my application locally using version 1.5.1 to make sure it still works
Deploy my application
Does my application start using version 1.5.1 of GAE once I do a deploy from v1.5.1 of the SDK?
Or do I need to switch to 1.5.1 using something like the App Engine Dashboard?
Is it possible to stay with version 1.5.0 indefinitely if I never download or use SDK version 1.5.1?
(I imagine this would be a bad idea)
Your application started using 1.5.1 as soon as Google deployed it to production. There's no way for you to control which version the production servers use; they'll all upgraded at the same time.
Is it possible to stay with version
1.5.0 indefinitely if I never download or use SDK version 1.5.1? (I imagine
this would be a bad idea)
Yes, it's possible. But it would be bad idea, because essential components of the cloud are being updated all the time. And you can probably miss critical updates or stuck with obsolete facilities of your local GAE server. For example, servlet container (Jetty), hadn't supported JavaEE 6 before it updated to 8.x version.