CraigsList is a good example of an application that uses subdomain routing as part of
their application.  This would be an extremely welcome feature.

(No comment was entered for this change.)

Just set it up on your dns host and fetch the subdomain from the wsgi app env

Or a full dns api would be nice.

Google is routing requests based on domain to particular application instances.  You
can't point a random domain at Google and get Google to route it like you want. 
Google Apps does offer one technique for changing the default *.appspot.com routing,
but it alone isn't enough to handle wildcards.

another request for wildcard subdomains, to allow users of my app to access their
page at username.myappdomain.com

Thanks!

Another request for this feature!  Thanks!

 Issue 130  is related as it requests multiple domains being able to point to the same
app. The two requests should be added to GAE together.

Another request for wildcard support.

A mobile app which requires minimal finger works from user will need that. 

This would also be very usedul to prevent XSS attacks with user provided HTML.

Another request for this feature please.

Has any progress been made on this issue?

It's really crucial to my business.

It would be good to have *.appname.appspot.com, already...

(No comment was entered for this change.)

Hi, we're about to launch our app without this, a feature we'd _really like_.

We've contemplated using urlfetch to make a nasty hack to log into our Apps control
panel and add each new subdomain as an alias for our application as needed, but are
confident that the awesome chaps on the App Engine team will fix this bug before we
resort to such barbarity.

;-)

About the hack, Google Apps has a limit on how many domain alias you can have so it
won't work in your case :-)

But do let us know if you have other hacks that work!

This feature would be really helpful--if you could either point *.example.appspot.com
or *.example.com to an application.

would another request help? well, it's being put in anyway :)

wow. i thought that this was already possible. my app is totally based on dynamic
subdomains. :-/

so... +1

This really is quite limiting without this type of feature. Would love to see the
priority set a little higher, instead of just "medium".

I need to have subdomains like live.sportschannel.com & score.sportschannel.com. This
is a big limitation. I wish priority was set higher.

sudhakar.sw,

You can add as many subdomains as you want in the google apps interface. You just have to manually add them 
and look for them in the request and handle accordingly. 

The problem here is that you can't have wildcards, so that *.sportschannel.com will work.

Thanks jeremy. I will give it a try. Hope that this doesnt affect cookies & SEO rankings.

I would like to have this too, *.mydomain.com, this would be a very useful feature.

isn't it more of google apps issue rather than google app engine -- as the app
engine's job is to just serve the request rather than bother about from where the
request came ... I think it should be in service setting of google app engine in
google apps  , is there "anywhere" where we can put google app issues similar to this ?

yes, I would like to have wildcards feature, please add this feature

I would like to have wildcards too.

This is my #1 problem

+1 I need this feature too, please make this happen Google.

Another vote

Would be nice

This is my top level problem.

i need this useful feature

Seems to be a recurring theme here :)

Press the star button to vote, I'm not sure why everyone feels the need to add "+1"
comments.

starred - as everyone else said, yes please!

I can't host my app on AppEngine without this  :(

I know it is not an ideal solution, but it is relatively simple to set up an nginx web 
server as a reverse proxy, you can then set custom http headers that that your 
application can read to determine what the subdomain is.

http://stackoverflow.com/questions/1022191/how-to-set-dynamic-subdomain-cross-server-
or-in-dns-setting

please see this

I know it is not an ideal solution, but it is relatively simple to set up an nginx web 
server as a reverse proxy, you can then set custom http headers that that your 
application can read to determine what the subdomain is.

need resolution to the wildcard of enom domain control.

Greetings, we launched this feature for all *.appspot.com domains with our 1.2.4 release.

For example:
  - http://www.shell.appspot.com/
  - http://foo.shell.appspot.com/

Currently we support one level of wildcard. So, if your app is named "bar", we
support serving on *.bar.appspot.com. We continue to also support direct serving of
specific major versions such as http://1.latest.shell.appspot.com/.

Serving wildcards on custom domains is still not supported. Also, availability of
https on wildcard subdomains depends on which browser you are using.

With that, I'm closing out this issue. Feel free to create separate issues for some
of the features here that we did not get to.

Cheers,
Jon

Hi Jon,

  I appreciate your hardwork. I do believe this issue is in regards to custom domains
and not appspot domains. Opening another issue will move it back to the bottom of the
pile. I would greatly appreciate it if you could reopen this issue.

  Some of the comments may have changed the meaning. However looking at the original
post I do believe it indicates custom domains.


Thanks,

Ethan

Hi Jon,

Agreed with @ethan on this -- the issue is very much about custom domains. In times when everyone and his 
dog has a domain name, I don't think many app developers are that interested in *.*.appspot.com domains...

Please reopen.

-- 
thanks, tav

Agreed with @ethan and @espians. No one cares about wildcards in appspot.com.

[]s

Agree too. appspot is just the sandbox, it's custom domains that need the wildcard

Same here -- it's all about custom domains.

Anyway it's great to see some progress!
But the original post and almost all comments (except one or two) were all about
wildcards on custom domains.
Reporting it fixed is just putting it in back of queue.
The original issue wasn't fixed. What's the point in issuing and starring same
feature-request multiple times?
Would please appengine team set status to some kind of "in progress", probably
accepted again?

I agree with the recent posters - I would think most people treat appspot.com as a test 
URL, migrating to a custom domain defore launching a product. Especially people who 
would be interested in fine-grained control of the URL...

Yeah.. it's only about custom domains. appspot is a test url

This is not fixing, but rather closing an eye on the problem.

Disappointed really. 

The original issue clearly talks about custom domains. The given example of this
feature working includes "domain.com" (ie. any domain) not "appsot.com". Why would
anybody want to make pretty, easy to remember individual subdomains for every user
and then settle for appspot.com, instead of their own domain?

I second the request for reopening this issue.

Sure thing, I see no harm in leaving this open. Apologies for the confusion.

Aha, figured out why I made such an obvious mistake. I had this issue confused with
 issue 861 . Sorry about that.

Thank you, Jon, for your time and hard work!
Looking forward for this issue to be resolved too, it's a must-have for many apps
that GAE is exactly for!

Would also like to see this.

this is partly a google apps problem than google app engine problem .. is there any 
issue list for google apps ???

I also agreed on a need to support wildcars on custom domains, thanks for the advance
on this issue almost one year later, maybe for the next birthday we will have it.

Thanks !

One solution to this would be to have an API to programatically add subdomains to
Google Apps. It would not be wildcard exactly - we would still need to set a CNAME
for each subdomain, but at least we would be able to add new subdomains within an app.

The workflow would be:
 
1. set CNAME for a new subdomain using the DNS provider API (or other ways, this is
not Google problem)

2. Add GAE app to Google Apps using the new subdomain, through Google Apps API. 

This doesn't seem to be a complex solution for such a hugely requested feature. All
we need is an API. As I understand, the existing one still doesn't allow this, even
for Premier accounts: http://code.google.com/apis/apps/

So I opened a new ticket asking for this feature. GAE team would have to work with
Apps team to provide this subdomains management API. Here it is:

http://code.google.com/p/googleappengine/issues/detail?id=2214

Another request :)

[%subdomain].appname.appspot.com

it would be cool if %subdomain would process as an incoming variable.

The hostname is in environ['HTTP_HOST'] (req.host with webapp/webob, req.get_host() on 
Django 1.0, req.META['HTTP_HOST'] on earlier Django versions), so you can figure out 
the subdomain at request-time from that.