This is not a bug report or a feature request. I simply wanted to take a moment to express my appreciation.
I previously tried to build a project similar to vey-proxy, with the goal of transparently intercepting, inspecting, auditing, and applying rules to HTTP/HTTPS traffic on a server without requiring changes to the application itself.
Once I started working on it, I quickly realized how many difficult and tedious problems are involved: transparent proxying, recovering the original destination, TLS interception and dynamic certificate generation, HTTP/1 and HTTP/2 handling, streaming request and response bodies, connection reuse, timeout handling, failure scenarios, audit pipelines, and many edge cases that are easy to overlook.
I encountered many difficulties along the way and spent a great deal of time dealing with low-level details.
Recently, I discovered VEY and saw what vey-proxy has already achieved. It made me genuinely happy. Many of the problems I had found extremely challenging have already been carefully implemented, organized, and maintained in this project. While reading the code and documentation, I could clearly feel the amount of engineering experience and long-term effort behind it.
I am very grateful to the author and all contributors for investing the time to open-source such a complex system and for continuing to maintain and improve it. This project saves others from a huge amount of duplicated exploration, and it has also given me a great deal of inspiration in terms of design and implementation.
I know that maintaining this kind of infrastructure project is not easy, so I wanted to leave this issue simply to say thank you.
I wish the VEY project continued success, and I wish all maintainers and contributors the very best.
Thank you again for your work.
This is not a bug report or a feature request. I simply wanted to take a moment to express my appreciation.
I previously tried to build a project similar to vey-proxy, with the goal of transparently intercepting, inspecting, auditing, and applying rules to HTTP/HTTPS traffic on a server without requiring changes to the application itself.
Once I started working on it, I quickly realized how many difficult and tedious problems are involved: transparent proxying, recovering the original destination, TLS interception and dynamic certificate generation, HTTP/1 and HTTP/2 handling, streaming request and response bodies, connection reuse, timeout handling, failure scenarios, audit pipelines, and many edge cases that are easy to overlook.
I encountered many difficulties along the way and spent a great deal of time dealing with low-level details.
Recently, I discovered VEY and saw what vey-proxy has already achieved. It made me genuinely happy. Many of the problems I had found extremely challenging have already been carefully implemented, organized, and maintained in this project. While reading the code and documentation, I could clearly feel the amount of engineering experience and long-term effort behind it.
I am very grateful to the author and all contributors for investing the time to open-source such a complex system and for continuing to maintain and improve it. This project saves others from a huge amount of duplicated exploration, and it has also given me a great deal of inspiration in terms of design and implementation.
I know that maintaining this kind of infrastructure project is not easy, so I wanted to leave this issue simply to say thank you.
I wish the VEY project continued success, and I wish all maintainers and contributors the very best.
Thank you again for your work.