deployed worker always returning 403 when uploading file via the routed domain.
Can someone help me with this behavior? It keeps returning 403 when I am trying to upload a file via the routed domain? it works fine when using the "workers.dev" domain/route.
Based on it's behavior, it seems like it didn't actually reach the worker because I don't see any 403 logs when I am trying to upload.
14 Replies
@Community Champion
@Cloudflare (Server Owner)
?pings
Please do not ping community members for non-moderation reasons. Doing so will not solve your issue faster and will make people less likely to want to help you.
Is the route set on your worker? I would suspect that or maybe something access/WAF related?
>I would suspect that or maybe something access/WAF related?
this is what I found in google/AI as well, but it really can be WAF even it's not activated yet?
what do you mean by "not activated yet"?
here,
that's just account-level waf, you will have zone-level waf enabled (it's default)
also I have another service worker that supports uploading file and it works fine, so it's really weird on this specific worker
what are the response headers
In the response headers, it shows that it's still "text/html"
on the other service, it shows "application/json"
cf-mitigated: challenge
that's WAF
you'll need to check your WAF events and see why it's being challenged