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.

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

HTTP2 Support #63

Closed
steelbrain opened this issue Sep 19, 2015 · 9 comments
Closed

HTTP2 Support #63

steelbrain opened this issue Sep 19, 2015 · 9 comments

Comments

@steelbrain
Copy link

Tracking bug for HTTP2. Post on here when there's a progress.

@bugok
Copy link
Contributor

bugok commented Sep 19, 2015

@steelbrain - what bug are you referring to?

@steelbrain
Copy link
Author

@bugok It's just that we haven't seen any thing or signal or progress on HTTP2 support in proxygen, just a note in a article in fb engineering which says it's In Progress™. so I thought I'd help you guys by creating a bug where you can post the progress 😃

@bugok
Copy link
Contributor

bugok commented Sep 20, 2015

@steelbrain
Copy link
Author

Now that's some progress 👏

@bugok
Copy link
Contributor

bugok commented Sep 20, 2015

Please track this folder. We're currently in testing mode for http2. When the code moved out of here - that means we've pushed it completely to production.

@bugok bugok closed this as completed Sep 20, 2015
@afrind
Copy link
Contributor

afrind commented Sep 21, 2015

Please feel free to give http/2 a try and let us know if you find any issues. I think HTTP2Codec is pretty mature and we'll be moving it out of /experimental/ soon.

@steelbrain
Copy link
Author

I don't use proxygen directly, I use proxygen + hhvm so no idea how to build/use experimental features with it 😛

@afrind
Copy link
Contributor

afrind commented Sep 21, 2015

The code is compiled in by default. You can configure HHVM to advertise HTTP/2 by adding this block to the Server section in a .hdf file:

SSLNextProtocols {
* = h2-14
* = spdy/3.1
* = http/1.1
}

I know HHVM uses .ini format externally but I don't know the exact syntax. This is just an array of strings under Server.SSLNextProtocols

@steelbrain
Copy link
Author

Thanks 👏

facebook-github-bot pushed a commit that referenced this issue Nov 18, 2019
…:FizzClientContext object to FizzClientContext (#63)

Summary:
This allows to remove various fizz specific parts of the API.
Pull Request resolved: facebook/mvfst#63

Test Plan:
Imported from GitHub, without a `Test Plan:` line.

 ---
## Proxygen Canary
Traffic Canary: https://our.intern.facebook.com/intern/traffic/canary?fbid=2326668697645016
* elb.prod.sju1c01 - binary - 2019-11-14 15:00 - https://fburl.com/dyndash/7m8qfbm6
* flb.prod.flhe2c01 - binary - 2019-11-14 15:00 - https://fburl.com/dyndash/alba0iv1
* olb.prod.rpnb0c01 - binary - 2019-11-14 15:00 - https://fburl.com/dyndash/f5eogqg5
* slb.prod_regional.rodn0c00 - binary - 2019-11-14 15:00 - https://fburl.com/dyndash/vtit218f
 ---

Reviewed By: yangchi

Differential Revision: D18303967

Pulled By: mjoras

fbshipit-source-id: 9bb7ed6ab608f9c2d1e8d5b0b533bda69f5d9a71
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants