-
Notifications
You must be signed in to change notification settings - Fork 459
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
SPDY Support #131
Comments
Thanks @tomsutton1984. At this point kraken.next will probably be the best bet for this feature (mostly because it will be a non-issue as developers will have control over transport directly.) If you get a second, please take a look at the branch and let us know if that will fulfill what you're looking for. Also, I'm content leaving this issue open until then just to make sure it gets addressed. |
I had filed a separate issue internally to have SDPY used by nginx for production instances. I'm guessing this is especially important since nginx terminates SSL for us and SPDY/SSL work together. Unless I'm missing something, adding the ability to kraken to support SPDY would just be nice to ensure it's flexible enough to do so for all around use cases (which is not a bad thing). |
Closing this out as this is a non-issue now that the .next branch has been merged into master. Middleware is entirely up to the app config and not buried in kraken. If you're daring, there's an early release candidate published on npm as |
Would be great to see the SPDY module integrated, auto fallback to http(s) if browser doesn't support SPDY
https://github.com/indutny/node-spdy
The text was updated successfully, but these errors were encountered: