Thank you for the help guys!
@Nick: I'm not using the URLFetch API so the *X-Appengine-Inbound-Appid *header
is not available. But it is good to know about this option too. Thanks.
--
You received this message because you are subscribed to the Google Groups
"Google App Engine" group.
To
Tamas,
You can implement application-level logic to only allow requests to your
service-name.project-id.appspot.com microservices from your own App Engine
projects by inspecting the *X-Appengine-Inbound-Appid* header.
More information can be found here for Python
Excellent question! Indeed, the service-name.project-id.appspot.com like
addresses should continue being accessible. You asked whether it's possible
to hide the back-end microservices from the public. A custom domain would
do just that, as the public is not normally aware of your project ID and
Hello George,
Thank you for your answer.
I still don't understand something. If I had my app engine application
running with a custom domain, wouldn't be my services still accessible via
the out-of-the-box provided service-name.project-id.appspot.com like
addresses?
--
You received this
Hello Tamas,
You may develop a front-end app that implements the micro-services
architecture and implement back-end functionality through endpoints. To
avoid exposing your endpoints directly, you may use your own domain, as
documented on the "Serving Multiple APIs from a Domain" page
