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

WebSocket doesn't work well when using VIP and authentication plugin using IP address #77

Closed
yush1ga opened this issue Oct 24, 2016 · 0 comments
Closed

WebSocket doesn't work well when using VIP and authentication plugin using IP address #77

yush1ga opened this issue Oct 24, 2016 · 0 comments

Comments

@yush1ga
Copy link
Contributor

yush1ga commented Oct 24, 2016

We have trouble with WebSocket function of Pulsar.

  • WebSocketService makes a client and the client connects Broker.
  • When the server for WebSocket is same as the server for Broker and when using VIP, a VIP member tries to connect with the VIP address.
  • When a VIP member is connected from a VIP member through VIP address, it behaves as if it is connected from not VIP member's address but VIP address because of loopback address setting.
  • When authentication plugin uses IP address information, authentication fails.
merlimat added a commit to merlimat/pulsar that referenced this issue Oct 24, 2016
@merlimat
Use local broker address as serviceURL when running WebSocket compone…
89a47d5 
…nt embedded in broker

Fixes apache#77
@merlimat merlimat mentioned this issue Oct 24, 2016
Merged
merlimat added a commit that referenced this issue Oct 25, 2016
@merlimat
Use local broker address as serviceURL when running WebSocket compone…
4d685b5 
…nt embedded in broker (#82)

Fixes #77
sijie added a commit to sijie/pulsar that referenced this issue Mar 4, 2018
@sijie
Revert dlog version to stable 0.5.0 (apache#77)
46d8874
hrsakai pushed a commit to hrsakai/pulsar that referenced this issue Dec 10, 2020
@cckellogg @merlimat
[ISSUE apache#72] Fix data race conditions. (apache#77)
bd30a32 
* [ISSUE apache#72] Fix data race conditions.

* Remove commented out code.

* Revert write request ch to unbuffered.
hangc0276 pushed a commit to hangc0276/pulsar that referenced this issue May 26, 2021
@jiazhai @sijie
Issue apache#61 : Fix unload and close broker error (apache#77)
30ae800 
Fix issue apache#61
We did not handle bundle unload very well. So in the situation that a topic is unload, the original kafka connection is still active, and topics still cached in KoP, this will cause error.
In this change, we track the topic loading status by register a mock producer in to PersistentTopic. when topic is unload, it will trigger the connection close.
Add new unit tests, make sure all tests passed.
@xiaotongwang1 xiaotongwang1 mentioned this issue Aug 4, 2021
Closed
@ZHr-UChiHa ZHr-UChiHa mentioned this issue Jun 3, 2023
Open
2 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@yush1ga