Hi there! I have a cf worker acting as a webhook to receive inbound email payloads. My inbound email parsing service calls this. Everything was working when I was using the workers dev route.
However, I wanted to add some firewall rules, and to do that I needed to add a custom route, so I can use my custom domain, and therefore make use of cf firewall rules. To add this custom route I followed: https://developers.cloudflare.com/workers/get-started/guide#optional-configure-for-deploying-to-a-registered-domain and setup my worker to serve traffic at
Then, as the guide says, I added an AAAA DNS record, targeting
100::, to make the domain resolve to the worker.
However, what I find is my inbound email parsing provider is no longer calling my webhook, and when I try to curl the route via
curl -v https://inbound.fwd.contact/ I get a
301 response. When I try the same URL in the browser, the redirect is followed and the expected response is shown.
I don’t think this 301 is actually correct behavior and I think the AAAA record should just call my worker right? Am I doing this right? Btw, I have https set to strict mode in my cf dashboard for this site.