-
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 3 replies
-
|
Hi @wenerme! I'm Dosu and I’m helping the orpc team. The batch endpoint likely fails behind nginx due to issues with response headers—especially To fix this, make sure that when you proxy or forward responses, you delete both the For debugging, log the raw request and response headers and bodies for your batch endpoint in both local and production environments. Compare them, focusing on those headers and the actual body size. This will help you spot where things diverge. SSE works because its streaming model and headers are simpler and less likely to trigger these issues with nginx. Batch endpoints, especially if they use chunked or streaming responses, are more sensitive to header mismatches and proxy quirks. To reply, just mention @dosu. How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other |
Beta Was this translation helpful? Give feedback.
-
|
Let try different mode: https://orpc.unnoq.com/docs/plugins/batch-requests#batch-mode |
Beta Was this translation helpful? Give feedback.
-
|
@unnoq the sevrer is hebind nginx reverse proxy the frontend send request to but the server unable to handle this how can i handle this ? |
Beta Was this translation helpful? Give feedback.

but I expeced to work with the original path
this seems resolve the problem