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.

Sign up for GitHub

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

Jump to bottom

[Client] Fix reading non-IPv4 remote address #38

Closed
clue opened this issue Nov 21, 2016 · 1 comment · Fixed by #64
Closed

[Client] Fix reading non-IPv4 remote address #38

clue opened this issue Nov 21, 2016 · 1 comment · Fixed by #64
Labels
bug easy pick help wanted invalid

Comments

@clue
Copy link
Owner

clue commented Nov 21, 2016

No description provided.

@clue clue added this to the v0.7.0 milestone Nov 28, 2016
@clue clue removed this from the v0.7.0 milestone Apr 14, 2017
@clue clue changed the title Fix reading non-IPv4 remote address [Client] Fix reading non-IPv4 remote address Apr 21, 2017
@clue clue added the invalid label Apr 21, 2017
@clue
Copy link
Owner Author

clue commented Apr 21, 2017

Can not reproduce this, looks like a bogus report :shipit:

@clue clue closed this as completed Apr 21, 2017
This was referenced Sep 1, 2017
Merged
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug easy pick help wanted invalid
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Fix SOCKS5 client receiving destination hostnames clue-labs/reactphp-socks
1 participant
@clue