Support custom domains (CNAMEs) for HTTP endpoint URLs
See original GitHub issueInstead of making HTTP requests to https://myendpoint.m.pipedream.net
, I’d like to couple a custom domain to a workflow and make requests to https://my.domain.com
, instead.
Issue Analytics
- State:
- Created 4 years ago
- Reactions:28
- Comments:12 (1 by maintainers)
Top Results From Across the Web
Using custom URLs by adding alternate domain names ...
To add an alternate domain name (CNAME) to a CloudFront distribution, you must attach to your distribution a trusted, valid SSL/TLS certificate that...
Read more >Tutorial: Add a custom domain to your endpoint - Microsoft Learn
Use this tutorial to add a custom domain to an Azure Content Delivery Network endpoint so that your domain name is visible in...
Read more >Custom Domains - Auth0
If you have a paid Auth0 subscription, you can use your own domain name (also known as a CNAME or vanity URL) on...
Read more >Configure Support for a Custom Domain - Oracle Help Center
To use a custom domain for your app you'll need to use your domain provider's tools to create a subdomain that points to...
Read more >How to CNAME to Amazon API Gateway Endpoint
The final step is to create a new CNAME Record in CloudFlare to link your domain to the CloudFront url. When you open...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Not yet, but this is still on our backlog! I shared this with the team
I need something like https://pipedream.mydomain.tld/ – not the “myname.pipedream.net” that was suggested. If I want JavaScript to run in a page and make an AJAX call to a pipe, an ad blocker may prevent the latter style from working. I’d pay for this feature such that new workflows with HTTP triggers are https://cname.mydomain.tld/some-string-for-the-endpoint/