-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Add instructions on how to use http2 with node.js enabled appengine #86
Comments
We sorta have support for HTTP/2. We terminate HTTP/2 connections at our load balancer, and then forward HTTP/1.1 requests to your application. We don't quite have HTTP/2 wired the whole way through to your app just yet. |
OK, that would be nice, so that I can avoid vulcanizing my resources and do something similar to https://github.com/GoogleChrome/http2push-gae |
* Port bookshelf to env:flex and Cloud SQL v2 * Add memcached (non-SASL) support to bookshelf * Change INSTANCE_CONNECTION_NAME to use config.json + check for it on prod * Fix typo
Moved to GoogleCloudPlatform/community#226 |
* updated CHANGELOG.md [ci skip] * updated package.json [ci skip] * updated samples/package.json [ci skip]
* updated CHANGELOG.md [ci skip] * updated package.json [ci skip] * updated samples/package.json [ci skip]
Co-authored-by: release-please[bot] <55107282+release-please[bot]@users.noreply.github.com>
🤖 I have created a release *beep* *boop* --- ## [0.3.4](https://togithub.com/googleapis/nodejs-video-live-stream/compare/v0.3.3...v0.3.4) (2022-11-11) ### Bug Fixes * **deps:** Use google-gax v3.5.2 ([#82](https://togithub.com/googleapis/nodejs-video-live-stream/issues/82)) ([f032c54](https://togithub.com/googleapis/nodejs-video-live-stream/commit/f032c546a3e61f4064439ed2a452c5d3fbeae8e8)) * Regenerated protos JS and TS definitions ([#86](https://togithub.com/googleapis/nodejs-video-live-stream/issues/86)) ([9942fd4](https://togithub.com/googleapis/nodejs-video-live-stream/commit/9942fd4f62d287df3e3d02d75f3eccb698edc62e)) --- This PR was generated with [Release Please](https://togithub.com/googleapis/release-please). See [documentation](https://togithub.com/googleapis/release-please#release-please).
🤖 I have created a release *beep* *boop* --- ## [0.3.4](https://togithub.com/googleapis/nodejs-video-live-stream/compare/v0.3.3...v0.3.4) (2022-11-11) ### Bug Fixes * **deps:** Use google-gax v3.5.2 ([#82](https://togithub.com/googleapis/nodejs-video-live-stream/issues/82)) ([f032c54](https://togithub.com/googleapis/nodejs-video-live-stream/commit/f032c546a3e61f4064439ed2a452c5d3fbeae8e8)) * Regenerated protos JS and TS definitions ([#86](https://togithub.com/googleapis/nodejs-video-live-stream/issues/86)) ([9942fd4](https://togithub.com/googleapis/nodejs-video-live-stream/commit/9942fd4f62d287df3e3d02d75f3eccb698edc62e)) --- This PR was generated with [Release Please](https://togithub.com/googleapis/release-please). See [documentation](https://togithub.com/googleapis/release-please#release-please).
* chore(main): release 2.1.1 * 🦉 Updates from OwlBot post-processor See https://github.com/googleapis/repo-automation-bots/blob/main/packages/owl-bot/README.md Co-authored-by: release-please[bot] <55107282+release-please[bot]@users.noreply.github.com> Co-authored-by: Owl Bot <gcf-owl-bot[bot]@users.noreply.github.com>
subject says it all
The text was updated successfully, but these errors were encountered: