You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have to use the server-sent event client that to requests non-GET method and request body. But It seems to me that this library does not support. For this I patched this and be using it.
From what I understand, there are the server-sent events used on HTTP endpoints with methods other than GET. For example, in OpenAI's public API, they require the use of the POST method and request body.
I have to use the server-sent event client that to requests non-GET method and request body. But It seems to me that this library does not support. For this I patched this and be using it.
From what I understand, there are the server-sent events used on HTTP endpoints with methods other than GET. For example, in OpenAI's public API, they require the use of the POST method and request body.
I've just run into this too, and I thought it was a spec thing but after a bunch of digging it appears the SSE spec does not mention anything about method constraints which implies any (logical) HTTP method is valid for initiating an SSE stream.
Unfortunately the API I'm talking to is not mine so I can't change it to use GET (which is what EventSource on the browser side uses, which seems to have set a precedent for SSE to appear "GET-only") so I'd like to see a method option added to the client constructor such as in this PR: #184
Hi, thanks share great library.
I have to use the server-sent event client that to requests non-GET method and request body. But It seems to me that this library does not support. For this I patched this and be using it.
From what I understand, there are the server-sent events used on HTTP endpoints with methods other than GET. For example, in OpenAI's public API, they require the use of the POST method and request body.
What are your thoughts on supporting this feature? If no problems, I'll be glad to help.
The text was updated successfully, but these errors were encountered: