Issue with RouteNotFound Error Due to Unpadded Base64url Tokens in HttpApi
I found something rather odd in HttpApi. I have a
Claude:
1. The @effect/workflow library generates unpadded base64url tokens (per RFC 4648)
2. When the signal name produced a token with length % 4 != 0 (like "select-move-out-date" → 103 chars)
3. Effect HttpApi treated the path parameter validation failure as "route not found"
POST/workflows/signals/:tokenDurableDeferredActivityselect-move-out-dateRouteNotFoundClaude:
1. The @effect/workflow library generates unpadded base64url tokens (per RFC 4648)
2. When the signal name produced a token with length % 4 != 0 (like "select-move-out-date" → 103 chars)
3. Effect HttpApi treated the path parameter validation failure as "route not found"
Similar Threads
Was this page helpful?
