-
Notifications
You must be signed in to change notification settings - Fork 305
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
SUBSCRIBE closes connection, does not keep-alive? #32
Comments
Fixed! This was a regression and is indeed not supposed to happen. |
Now the connection stays properly open and data is transferred, thanks, but the HTTP headers are still missing. For example, Content-Type: application/json
Date: Mon, 03 Jan 2011 20:43:36 GMT
Transfer-Encoding: chunked
(and the empty line)
|
You are right, sorry about that; most of the issues with pub/sub are regressions from a previous change and it seems that there were still problems with pub/sub. Please try the latest master, I have just pushed a fix and confirmed that headers are sent properly. |
Thank you again, now it works beautifully. |
I'm unable to subscribe to a channel through HTTP. It appears the connection gets closed as soon as the subscription is done, and that HTTP headers (ie. content-type) are completely missing from the response. Should it work?
The text was updated successfully, but these errors were encountered: