Skip to content
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.

Sign up for GitHub

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

Jump to bottom

server: Flush headers when using wait=true and stream=true #877

Merged
merged 1 commit into from
Jul 8, 2014
Merged

server: Flush headers when using wait=true and stream=true #877

merged 1 commit into from
Jul 8, 2014

Commits on Jul 3, 2014

  1. server: Flush headers when using wait=true and stream=true 

    Many http clients will missbehave unless they get an initial http-
response, even when long-polling. It also saves the user/client from
having to handle headers on the first action of the watch, but rather
handle the response immediately.
    Christoffer Vikström committed Jul 3, 2014
    2 Configuration menu
    Copy the full SHA
    2338481 View commit details
    Browse the repository at this point in the history