apache / apache/pulsar

About proxy support in Client Lookup phase

Open
#15,007 3 comments 0 reactions 0 assignees View on GitHub
lifecycle/stale Stale type/feature
Dominant language
Java
Stars
15.3k
Forks
3.8k
Avg merge
1d 14h
Merged PRs (30d)
160

Description

In some scenarios, the client lookup also needs to access the network through HTTP or socks proxy. The current version does not support. I fork a version that supports this feature. Is it possible to incorporate it into the pulsar code?

My fork url:
https://gitee.com/liufbox/pulsar.git

Contributor guide

Open the contributing guide

Research direction

Start by reviewing the client lookup implementation in the Pulsar repository and the proposed changes in the linked fork at https://gitee.com/liufbox/pulsar.git. Determine how HTTP and SOCKS proxy support should be incorporated into the lookup path; done means both proxy types work for client lookup and the relevant behavior is covered by tests.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
networking
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.