update main dependencies

[hoodie]

Hi there,
I've noticed that some deps are out of date and thought I'd give it a try.

What do you think?

[jselig-rigetti]

Hope to see this MR merged soon. Currently facing https://rustsec.org/advisories/RUSTSEC-2023-0052 from this.

[jselig-rigetti]

Looks like this should supersede #28, #30, and #31

[hoodie]

ping @tafia

[jselig-rigetti]

@tafia please consider this change.

[hoodie]

@jselig-rigetti I think for your usecase you should probably look at http-proxy2. I just found that when I published my changes to https://github.com/goto-opensource/hyper-proxy 🙄 😆

[jselig-rigetti]

@jselig-rigetti I think for your usecase you should probably look at http-proxy2. I just found that when I published my changes to https://github.com/goto-opensource/hyper-proxy 🙄 😆

I'd looked at it, but it has an http = "1.0" dependency which conflicts with tonic since it depends on http = "0.2" so I ended up forking this repo. Thank you though!

[hoodie]

oh boy, there are a bunch of forks of this now 😆
I was about to publish my version as hyper-proxy2 until I saw that other one. And naming things is sooo hard.

[wyatt-herkamp]

oh boy, there are a bunch of forks of this now 😆 I was about to publish my version as hyper-proxy2 until I saw that other one. And naming things is sooo hard.

About to do the same.

[hoodie]

@wyatt-herkamp feel free to pull from my fork

[aviramha]

@hoodie did you end up publishing? (your fork looks the most mature)

[hoodie]

No because there already is hyper-proxy2

[aviramha]

We had some issues with hyper-proxy2, also some that would do breaking changes - we created https://github.com/metalbear-co/hyper-http-proxy which is also published to crates.
We removed openssl support (just because it took time to adjust the fixes and we didn't care about it)