Paul, Thank you for your reply.
Are you asserting that the documentation at https://cloud.google.com/appengine/docs/python/how-requests-are-routed is obsolete? - Aaron On Thursday, September 15, 2016 at 3:24:56 AM UTC-7, Paul Canning wrote: > > Some of the app engine console was updated. > > Instead of setting a "default" version, it now uses traffic splitting. So > your live version is the default, as it gets 100% of the traffic. > > I also believe you cannot dispatch to specific module versions. > Dispatch.yaml only allows routing to a module (the version is then > determined by the traffic splitting) > > NB - if you had two separate modules, you would need to use a > dispatch.yaml to assign the custom domains, it is not done automatically. > > On Thursday, September 15, 2016 at 2:26:26 AM UTC+1, Aaron Alpar wrote: >> >> We have an Appengine application that has long used the version routing >> described in the "Routing via URL" section of >> https://cloud.google.com/appengine/docs/go/how-requests-are-routed. >> >> We have two version of our application, "live" and "master". "live" is >> our production application, while "master" is used for testing. >> >> We have a custom domain, "taviti.com" assigned. >> >> Normally we use "https://live.taviti.com"; to access our live site and " >> https://master.taviti.com"; to access our testing site. Using this >> convention takes advantage of the default version routing described in the >> "how-requests-are-routed" page to route traffic to our production or test >> versions. >> >> The problem is that "https://master.taviti.com"; is routing to our *live* >> site. This condition persists despite: >> >> - We don't have any rules in our "dispatch.yaml" file that conflict with >> the default routing described in the "how-requests-are-routed" document. >> >> - We do have Custom Domains, but the "master" versions, for test, all >> appear to point at "master.taviti.com". >> >> - Curiously the Google Cloud Console, "Appengine", "Versions" tab shows >> live receiving "100%" of the traffic, although we don't use traffic >> splitting. >> >> We can access our test site through the "appspot.com" although its not >> completely functional. >> >> My questions: >> >> Have there been any recent changes to how requests are routed? >> >> How can I discover is traffic splitting is turned on, and how do I turn >> it off? >> >> What else can cause all the traffic to all custom domain names to be >> routed to one version of our Appengine application? >> >> - Aaron >> > -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-appengine+unsubscr...@googlegroups.com. To post to this group, send email to google-appengine@googlegroups.com. Visit this group at https://groups.google.com/group/google-appengine. To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/a53983e7-8718-435d-a06c-52f491733a0e%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
