Hi Matt, On Mon, Dec 7, 2009 at 9:52 PM, Matt P <[email protected]> wrote:
> > This part appears to make sense: > > > > "If eNom is your service provider: > > - Add a Host Record with @ as the Host Name, the url of the home page > > of your Site as the Address, and URL Frame as the Record Type > > - Change or add a CNAME of www so it points to the symbol @ > > - Save the changes and WAIT for up to 48 hours for the changes to > > propagate to all necessary world-wide servers." > > > > Or look at eNom's doc. > eNom's doc doesn't really cut it -- what is confusing is how google > figures out what pages to display.. a lot of it seems to be automatic, > looking at the actual request.. but that wasn't obvious when I sat > down to take care of this. > > Regarding eNom's URL frame.. that solution isn't great. It doesn't > get along with App Engine's cookie mechanism for sessions. When I > reload a page, session data is gone. (using appengine_utilities for > sessions) > > For now I'm just redirecting to my app engine URL. Not pretty but it > works. I ended up using the exact paragraph you quote (just using > the URL Redirect instead of URL Frame) > > Seriously Google. Come up with a solution to this & put the docs > online. You sent me to eNom -- you should take care of documenting > their system in regards to this need -- a need that LOTS of people > will want. > The Knol you're referring to is linked under a section "URL Forwarding for Google Sites" - this applies to Google Sites, not to App Engine. The instructions that are relevant to App Engine are in the section above this, where it says: If you'd like to allow users to enter example.com and arrive at your web > pages at www.example.com, we recommend creating a Javascript redirect, or > a 301/302 redirect to point your users to the intended destination. Since > instructions vary by domain host, we recommend contacting your hosting > service for further instructions. As the text says, because the details of setting up a redirect for your naked domain varies from provider to provider, it's not possible for us to exhaustively document this. To answer your more general question, routing to App Engine apps depends on the mappings you have configured in Google Apps. When our infrastructure receives a request for a domain name, it checks to see if a mapping exists in Apps, and if it does, redirects it to App Engine (or another service, as appropriate). In the absence of a mapping, it serves up a generic 404 page. In order for traffic to reach our infrastructure, the domain in question has to have a CNAME record to ghs.google.com, which is not possible for naked domains; hence the requirement of a workaround via an external service that sends 301 or 302 response. -Nick Johnson > Matt > > -- > > You received this message because you are subscribed to the Google Groups > "Google App Engine" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]<google-appengine%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/google-appengine?hl=en. > > > -- Nick Johnson, Developer Programs Engineer, App Engine Google Ireland Ltd. :: Registered in Dublin, Ireland, Registration Number: 368047 -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
