Skip to content

WIP: Add TLV support and general refactorings #2

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

Closed
wants to merge 4 commits into from

Conversation

Freeaqingme
Copy link
Contributor

Hi,
I was looking for proxyprotocol support for Golang where I could encapsulate a listener like what is possible with https://github.com/armon/go-proxyproto , except I needed to use version 2 with TLV.

Therefore I was happy to find your repo, and took the liberty to extend it a bit here and there. It's still a WIP, though I'm curious what you think about the (albeit also still-in-progress) API.

Dolf

  • Freeaqingme

@@ -0,0 +1,152 @@
package proxyproto
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just realized I forgot to add any copyright notice, will at least add that it's derived from https://github.com/armon/go-proxyproto/blob/master/protocol.go

@pires pires self-assigned this Jun 22, 2017
@pires
Copy link
Owner

pires commented Jun 22, 2017

I like the idea of the connection wrapping even though it seems out-of-scope for this library. However, don't like the fact the API is broken with this change.

It's been some time since I last picked on this so I'll need to take a few hours to review properly.

@jeffreydwalter
Copy link

@pires are you planning on merging these changes? I am also interested in support for v1 and v2 with the Listener interface.

@pires
Copy link
Owner

pires commented Oct 25, 2017

I'd like to merge it, yes but, unfortunately, I haven't had the time to properly review it. The fact it breaks the existing API is also doesn't help.

@pires pires closed this in #8 Jun 15, 2019
@pires pires reopened this Jun 15, 2019
@pires
Copy link
Owner

pires commented Jun 15, 2019

Sorry for closing, it was accidental.

@pires
Copy link
Owner

pires commented Jun 15, 2019

Would be cool if you could resume the TLV support based on current master branch 🙇

@Freeaqingme
Copy link
Contributor Author

Good job on #8 , was planning of reviewing it later, but you move fast :)

Right now I've got different priorities so can't tell when I'll revisit this (same goes for golang/go#20956 ). Having said that, I do expect to be working on some HTTP projects later this year when I'll surely need something similar.

Though, if that takes too long, I by no way would take offence if someone else would continue this work.

@pires
Copy link
Owner

pires commented Jun 15, 2019

Sorry, I should've waited indeed. I may be back to this PR and try and adapt your TLV work. Thank you very much!

@dekimsey
Copy link

Apologies for the drive-by I was looking into the package for a Vault issue I'm curious about. But how might this compare against the PR on elastic's fork here? It seems to have a similar goal of supporting TLVs in go-proxyproto.

@Freeaqingme
Copy link
Contributor Author

@dekimsey I'd ask the author of that PR. Chances are he's seen this PR as well, and he can explain why he thought one way to go about it would be better than another.

@pires
Copy link
Owner

pires commented May 7, 2020

Hey @Freeaqingme! Thank you for your involvement so far in helping w/ this library. Is there anything from this PR that you think is missing from the current tip?

@pires
Copy link
Owner

pires commented Oct 17, 2020

Thank you very much for your contribution even if it didn't get merged.

@pires pires closed this Oct 17, 2020
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

Successfully merging this pull request may close these issues.

4 participants