It needs to be to the same hostname
It needs to be to the same hostname
Jhmm, what do you mean by that? It's actually really strange, if I curl my endpoint it works fine, the request goes to my worker
Jbut requests from the 3rd party service that's calling my webhook don't come through.. for whatever reason
Jif I switch the url to anything else, e.g. webhook.site .. the 3rd party service's webhook call comes through fine
Jso it works, but something is behaving differently
WOh whoops netlify
Jor cloudflare? or the caller of the webhook
Jso hard to debug
WIf the webhook caller doesn't give you more details (e.g. a status code or attempts or anything) then I'd ask them
WPossible they're being challenged
WYou could check security events
Jyeah, it's an organisation that's really hard to communicate with.. I'm kind of treating it like a black box right now
Joh interesting, let me see if I can figure out how to do that
J@Walshy | Deploying oh wait, but that requires having a zone
JI'm just using a CNAME subdomain with pages
Wwhere does cloudflare fit in here? 
Jcloudflare pages?
JI was previously trying with a worker and a netlify rewrite pointing at it, but thought I'd try using cloudflare pages with a custom domain instead to see if that helped
Jexactly the same issue
JI think you might be right that it could be some kind of security challenge
Wok so it is pages
Wyou said netlify so it was very confusing
WPages proxying doesn't allow cross-hostname
Was I mentioned at the start
Wso, that part will never work
WNow is this a Worker or a Function?
JI'm not using pages proxying
J_worker.js
WThis is getting very hard to follow :LuL:
WWhat is your actual setup?
Ja simple _worker.js in a pages project, set up with a custom domain foo.example.com. it successfully receives requests, including a different webhook from the same source. the other webhook (a body full of XML) never gets to my worker
Wyeah check security events, if nothing in there then cf seems to be fine
JI don't think I have anywhere to check security events
Woh right external dns
Wthen yeah this isn't a cf issue
Wi'd chat to that caller that isn't working
Jit just seems impossible that it isn't a cf thing.. because if I cname foo.example.com to a different domain the request comes through
Jdo you say this because cf wouldn't be applying any firewall in that case?
Wyup
Joh crazy
JI'm literally stumped then. I don't see how the sender of a http request would fail to send that request only if the domain they are sending to ends up going to a cloudflare worker
Jthe fact that it also doesn't work when transparently tunnelled through a netlify site makes me think that cf must not be allowing the request through based on what it looks like, rather than it being a problem with the sender
Jbut I appreciate the fact that I don't control the sender makes it hard to debug
Jhence spending a whole day trying to figure this out 
NI couldn't find a pricing calculator for the standard pricing model, so I created one:
https://standard-model-pricing-calculator.pages.dev/
https://standard-model-pricing-calculator.pages.dev/
J@Walshy tried putting the same code on deno.deploy and forwarding requests to that and it works fine 
WStill doesn't point to cf sadly haha
WWe've seen sites do weird things when going to CF IPs
WI can't think of anything on CF that would prevent it, so if you're sure your code isn't invoked. I'd talk to that sender
Jyeah, I really don't know enough about networking and http to know where a problem could come from
J@Walshy but the fact that the request is going via a netlify rewrite should mean that to the requester it makes no difference where the response ultimately comes from, and it's impossible to tell
