Hello Daniel 

As you referred to the issue discussed in this 
<https://stackoverflow.com/questions/41160448/google-app-engine-redirecting-all-naked-domain-requests-causing-letsencrypt-to>
 
Stackoverflow link, I went through a couple of cases related to “xxx domain 
is already mapped to a project “ . In order to solve this, you would need 
to use the API 
<https://cloud.google.com/appengine/docs/admin-api/reference/rest/v1/apps.domainMappings/create>
 
which will let you overwrite the existing mapping, however, please keep in 
mind that doing this will probably stop other products for serving as if 
the domain is mapped on another App Engine, that app will no longer serve 
from this domain.

You can use the following steps in order to execute the API:

1) Go to this 
<https://developers.google.com/apis-explorer/#search/admin%20api/appengine/v1/appengine.apps.domainMappings.create>
 
link.

2) Fill out the request form and enable OAuth2.0 Under the request body on 
the id parameter, put your naked domain. 

3) Execute the command, which will require you to authenticate with Google

4) To enable Google's built-in SSL support (Optional): Select your 
subdomain from the table of custom domains under App Engine settings and 
click the "Enable Managed Security" button.

I found this solution 
<https://groups.google.com/forum/#!topic/google-appengine/xycWwRX2OiU> 
worked for many people, so I would recommend you to try this. If you still 
having this issue, Please open a private issue in issue tracker 
<https://issuetracker.google.com/>. Please provide the output of this [1] 
command in the body including detailed description of your issue. Which 
will allow us to investigate your project in depth.

[1] gcloud info --anonymize


On Monday, October 1, 2018 at 12:52:17 AM UTC-4, Daniel Young wrote:
>
> I found I'm having this exact issue 
> https://stackoverflow.com/questions/41160448/google-app-engine-redirecting-all-naked-domain-requests-causing-letsencrypt-to
>
> On Sunday, September 30, 2018 at 5:58:00 PM UTC-7, Daniel Young wrote:
>>
>> In the browser address bar in chrome/firefox if I type in '
>> example.com/full/path'
>>
>> It redirects to https://www.example.com. If I type the full path (
>> https://www.example.com/full/path) in the address bar there is no 
>> problem.
>>
>> I have https required in app.yaml
>>
>> - url: /.* script: myapp.app secure: always redirect_http_response_code: 
>> 301
>>
>> However, some shorter paths work in the address bar, if I type in '
>> example.com/help' it routes fine to the https://www.example.com/help.
>>
>>
>> I can't tell if the issue is in app.yaml, the dns records, or somewhere 
>> in a browser settings.
>>
>

-- 
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 [email protected].
To post to this group, send email to [email protected].
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/94fb8db3-f4e6-4e28-81ef-95a8090bee50%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
  • [google-appe... Daniel Young
    • [google... Daniel Young
      • [go... 'Amit (Google Cloud Support)' via Google App Engine
        • ... Daniel Young
          • ... edgaralexander via Google App Engine
            • ... 'Edgar (Google Cloud Platform Support)' via Google App Engine

Reply via email to