Closed niksrc closed 5 years ago
Merging #245 into master will decrease coverage by
0.06%
. The diff coverage is0%
.
@@ Coverage Diff @@
## master #245 +/- ##
==========================================
- Coverage 62.22% 62.16% -0.07%
==========================================
Files 50 50
Lines 4072 4076 +4
==========================================
Hits 2534 2534
- Misses 1350 1354 +4
Partials 188 188
Impacted Files | Coverage Δ | |
---|---|---|
internal/proxy/logging_handler.go | 14.75% <0%> (-1.04%) |
:arrow_down: |
Merging #245 into master will decrease coverage by
0.06%
. The diff coverage is0%
.
@@ Coverage Diff @@
## master #245 +/- ##
==========================================
- Coverage 62.22% 62.16% -0.07%
==========================================
Files 50 50
Lines 4072 4076 +4
==========================================
Hits 2534 2534
- Misses 1350 1354 +4
Partials 188 188
Impacted Files | Coverage Δ | |
---|---|---|
internal/proxy/logging_handler.go | 14.75% <0%> (-1.04%) |
:arrow_down: |
Hi @niksrc,
Thank you for the contribution! We'll get this reviewed and responded to properly in the coming days (early next week most likely).
Thanks for your patience!
@Jusshersmith Any update on this?
I've completely failed to follow up on this, for which I am extremely sorry!
I am however now actively testing this change.
There are some followup additions I'd like to land (such as another test, and some documentation changes), though seeing as this is a fork and to expedite this pull request, I'll add these afterwards in a new pull request.
Thanks for your patience on this everyone, and thank you again for the contribution @niksrc!
Great work! When will it be released?
Hey @yacut. We're planning on publishing a release this coming Monday!
Problem
Add support for WebSockets
Solution
What is the proposed solution? Since we started building on go1.12 with native WebSocket proxy support, the only thing needed is to implement
Hijacker
onresponseLogger
to support WebSockets. Fixes #103Notes
To proxy WebSocket successfully, an appropriate flush_interval is required. This pr is tested to proxy weave-scope with a flush_interval of 0.1s