-
-
Notifications
You must be signed in to change notification settings - Fork 260
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/HTTP3/Quic feature request for next generation communication testing #446
Comments
hey, in my plans, http2 will come AFTER i'll be done with 0.xx versions, which will hopefully happen before summer. HFS is based on node.js, that currently supports HTTP2 but not 3. |
@rejetto First I would like to thank you for the amazing tool one of the best and I use it heavily in my test cases. Now why do I need this feature again for my test cases where I use HTTP2 and HTTP3 traffic to inspect against perimeter devices and create rules according to test if things work fine with these protocols or performance issues? and I had faith that if I put in my request I would get the feature in future releases ... HTTP3 is basically use Quic protocol which next-gen communication and gonna accept my all vendors and firewalls |
i'm really happy to know that you like it! |
@rejetto I use HFS to download and upload files and put a firewall between HFS and the client then use HTTPS traffic to inspect the encrypted traffic. now rest test cases firewall-specific but the key protocol that I test is HTTP2/HTTP3/Quic and for this purpose, I need HFS to support these protocols as HFS implementation is very simple and fast. otherwise, I have to spin a webserver based on NGINX or Apache which needs lots of effort setting up the server. Here HFS shines and save my time and quickly setup webserver in no time |
Hello Expert,
Currently, HFS support only HTTP1.1 version. is it possible to add HTTP2/HTTP3/Quic protocol support in future releases for next-generation protocol testing? your tool is a life saver and hoping for these feature additions soon.
The text was updated successfully, but these errors were encountered: