a newbie trying to deal with DNS settings is a mess, plus it's boring to wait and see if it worked, so I decided to come back here and tell more detailed steps on how to solve this before google does ;)
Google Apps tells you to insert 4 A records pointing to 4 google IPs. How to reach it: Domain Settings, Domain names ( https://www.google.com/a/cpanel/mydomain.com/DomainSettingsDomains ) Then you need to set which subdomains you want to listen in yourdomain.com and point to your appengine app. Yes, you can now set the * wildcard (this is what I'll use for the CNAME later). How to reach it: Dashboard, your Google App Engine project ( https://www.google.com/a/cpanel/mydomain.com/AppEngineServiceSettings?appId=myappengineid ) Google Apps recommends you to do this on your DNS settings: mydomain.com A -> google 4 IPs * CNAME -> ghs.google.com But I've changed it to (replace 'app' with your desired subdomain): app.mydomain.com A -> google 4 IPs * CNAME -> ghs.google.com app A -> your regular hosting IP then, on your regular hosting (hostgator in my case, godaddy for others), create a .htaccess on the root with this content: RewriteEngine on RewriteCond %{HTTP_HOST} ^mydomain.com$ RewriteRule ^(.*)$ "http\:\/\/app\.mydomain\.com\/$1" [R=302,L] this way you keep google apps handling everything except the naked mydomain redirection. your regular hosting will be foing the naked domain redirection preserving full path (as described in this .htaccess), redirecting it to app.mydomain.com/full/path (and from there forward it's back on google's hands). it's a good way to fix this problem by yourself, until google fixes their redirector (I've already warned about the problem on Google Apps). On Apr 9, 3:59 pm, Robert Kluin <robert.kl...@gmail.com> wrote: > If you read back through this entire thread you'll see some discussion > on that issue. Perhaps people are generally using some other > forwarding service. > > Robert > > > > > > > > On Sat, Apr 9, 2011 at 04:36, roberto.cr <roberto...@gmail.com> wrote: > > TL;DR > > > Google is not redirecting my naked domain preserving full path. > > Examples: > > mydomain.com -> app.mydomain.com CORRECT > > mydomain.com/login -> app.mydomain.com WRONG ( should've pointed to > > app.mydomain.com/login ) > > john.mydomain.com/login -> john.mydomain.com/login CORRECT > > > Does this happen to *everyone* ??? How come there's not much info > > about it on this discussion group ? > > How are people solving this ? > > > On Apr 8, 10:29 pm, "roberto.cr" <roberto...@gmail.com> wrote: > >> I'm having the same problem! > > >> I've set (under google apps cpanel DomainSettingsDomains) google apps > >> to redirect mydomain.com to app.mydomain.com (because appengine > >> doesn't allow for naked domains anymore) > >> Then I've set (under google apps cpanel AppEngineServiceSettings) app > >> engine to listen to *.mydomain.com (yes, you can set the * wildcard > >> there now) > >> This worked almost perfectly, but the only thing off is actually the > >> most important: > > >> mydomain.com would redirect to app.mydomain.com > >> userinput.mydomain.com would keep the userinput and load my regular > >> app.mydomain.com (as described in my app.yaml, having my app to treat > >> "userinput": in Python's webapp framework you can access this with > >> self.request.headers['Host'] ) > >> userinput.mydomain.com/login would keep the url but behave like > >> app.mydomain.com/login (as expected) while still being able to read > >> "userinput" > >> BUT mydomain.com/login would NOT redirect to app.mydomain.com/login ! > >> it simply redirects to app.mydomain.com ignoring the full path! > > >> the problem seems to be the way google redirects my naked domain. it > >> ignores the full path. I guess it's not just me, is it? > > >> so you are saying the solution really involves setting everything up > >> on godaddy ? > >> (in my case hostgator. I bought a .to domain, set the NS to my regular > >> hostgator account and setting all DNS settings there.) > > >> On Apr 2, 1:13 am, Thomas Wiradikusuma <wiradikus...@gmail.com> wrote: > > >> > Hi Giacinto, > > >> > I'm having exactly the same problem. Can you get into more detail > >> > (step-by-step, starting > >> > fromhttps://www.google.com/a/cpanel/MYDOMAIN/DomainSettingsDomains > >> > probably?) on how you get it done? I understand your post, but I'm > >> > afraid I might click/delete the wrong stuff. > > >> > On Mar 31, 2:31 am, Giacinto <decata...@gmail.com> wrote: > > >> > > Well, i solved the problem! None of the previous solutions is really > >> > > the > >> > > good solution, or better, none is complete. The real problem of the > >> > > lost > >> > > request's full path is the google autosetting for wwwredirect! > > > -- > > You received this message because you are subscribed to the Google Groups > > "Google App Engine" group. > > To post to this group, send email to google-appengine@googlegroups.com. > > To unsubscribe from this group, send email to > > google-appengine+unsubscr...@googlegroups.com. > > For more options, visit this group > > athttp://groups.google.com/group/google-appengine?hl=en. -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to google-appengine@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
