Daniel
Explore posts from serversCDCloudflare Developers
•Created by Daniel on 3/14/2025 in #workers-help
Limit [wrangler:inf] logging without setting --log-level
Any news here?
2 replies
CComposioHQ
•Created by eastern-cyan on 4/1/2025 in #🖥│support-forum
Any plans to add pagination to GOOGLEDRIVE_FIND_FILE action?
You guys are amazing!
6 replies
CComposioHQ
•Created by national-gold on 4/1/2025 in #🖥│support-forum
Any plans to add pagination to GOOGLEDRIVE_FIND_FILE action?
Thank you for the quick response
6 replies
CComposioHQ
•Created by inland-turquoise on 3/10/2025 in #🖥│support-forum
[Solved ✅] Cloudflare ComposioError: Request with a GET or HEAD method cannot have a body.
@Damiano Rodriguez It seems they just merged my fix, so maybe a new release will come soon 🙌
9 replies
CComposioHQ
•Created by other-emerald on 3/10/2025 in #🖥│support-forum
[Solved ✅] Cloudflare ComposioError: Request with a GET or HEAD method cannot have a body.
9 replies
CComposioHQ
•Created by ambitious-aqua on 3/10/2025 in #🖥│support-forum
[Solved ✅] Cloudflare ComposioError: Request with a GET or HEAD method cannot have a body.
The error happens because the Cloudflare JavaScript runtime (Wrangler) enforces that HTTP GET requests must not have a body (which I believe is quite reasonable, but the HTTP protocol doesn't explicitly forbid it).
There are a few places in the Composio codebase where a body is sent in a GET request. Usually it contains
{useCase: parsedData.useCase} - I'm not a 100% certain on what this is, but I can see that removing this code solves the problem when removed. This should be safe to do, because the useCase parameter is already submitted as a query parameter in this GET request.
After a brief inspection of the codebase, I can see that the same problem also appears in findActionEnumsByUseCase in js/src/sdk/models/actions.ts - but I have decided to not change it there, as this parameter does not exist in the query parameter.9 replies