Status Update
No update yet.
Comments
ma...@bigwavelabs.co
Hello,
Thank you for reaching out to us!
I tried to reproduce this issue at my end. However, I am getting the intended behavior.
Please check the
Please let me know if that helped you with your use case and if there is anything else you would need assistance with.
Thank you
ji...@google.com
ji...@google.com
> Scheme
> JavaScript origins must use the HTTPS scheme, not plain HTTP. Localhost URIs (including localhost IP address URIs) are exempt from this rule.
Subdomains of localhost (ie. foo.localhost) *are* "Localhost URIs" but are not currently exempt from the rule, contrary to the documentation.
os...@einride.tech
Hello,
Thank you for reaching out to us with your request.
We have duly noted your feedback and will thoroughly validate it. While we cannot provide an estimated time of implementation or guarantee the fulfillment of the issue, please be assured that your input is highly valued. Your feedback enables us to enhance our products and services.
We appreciate your continued trust and support in improving our Google Cloud Platform products. In case you want to report a new issue, Please do not hesitate to create a new issue on the
Once again, we sincerely appreciate your valuable feedback; Thank you for your understanding and collaboration.
ma...@google.com
Commenting in behalf of customer:
They wish to have this feature for the following reason:
The ".dev" as this makes it seem like dev, not production, and have been challenged on this by clients saying they do not want dev, deployed to production, which we know is incorrect, but adds a lot of confusion!
We have over 500,000 users in one production environment, we have not seen any loss of revenue yet, but have wasted time in explaining to clients what ".dev" means.
na...@kyocera.jp
The REST API for customers should be able to be published in our own domain, and the configuration combined with Cloud Load Balancing is complicated.
Description
Please describe your requested enhancement. Good feature requests will solve common problems or enable new use cases.
What you would like to accomplish:
Map a custom domain to an API Gateway, e.g. map
How this might work:
Cloud Run already has the feature so I guess it would be similar. You point out the domain you want, add the necessary registries in the DNS provider and wait the verification
If applicable, reasons why alternative solutions are not sufficient:
Other information (workarounds you have tried, documentation consulted, etc):
Tried setting it through a CNAME record and setting a Load Balancer in front of the gateway, as suggested in the official documentation