-
Notifications
You must be signed in to change notification settings - Fork 209
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
BIG PROBLEM! Using gRPC streaming the call stays in pending state (and doesn't work) if I use LoadClientStateMiddleware, works if not. #325
Comments
@timostamm just answered:
|
@aarondl can you please help me here? 🙏 |
Hi there @frederikhors. Not sure how to help here, it's not built that way. |
What do you mean? |
Why is the response not closed? |
The response is always closed, it's a guarantee by the stdlib nowadays. Now because you're using grpc in some fashion that might be different maybe they're doing their own weird http things. Authboss's middleware is pretty simple, when a request comes in it gives the request to LoadClientState which gives it to your But I'd suggest reading client_state.go and take a look at the |
See the answer from @johanbrandhorst here:
I'll report your answer to his amazing team. |
I have been using authboss for a long time (it's such a pleasure, THANKS!).
I'm using it with a grpc-web server too.
Today I had to test the gRPC server streaming and after HOURS of trying I realized that it is authboss that causes a strange issue described below:
I'm trying to use protobuf-ts but I don't get messages from server until connection is closed.
I'm using Svelte 3 like this:
The call in in pending state for about 2.2 min. After that I get all messages logged in console.
If I change this line:
to:
(removing
authb.LoadClientStateMiddleware
) it works!Why?
@aarondl, this is HUGE! Can you please help me solve it?
The text was updated successfully, but these errors were encountered: