You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The edge router is attempting to read the 4-byte magic number for the edge-protocol message, but gets zero bytes instead. The error is unrecoverable on edge router side, so it closes the channel.
The client side then gets confused, and the attempt to decrypt incoming traffic/responses, manifests an error:
Could not decrypt record or bad MAC
There seems to be some kind of async/timing differences, or websocket data-chunking differences, concerning how things operate on these two browsers while running the exact same code.
The text was updated successfully, but these errors were encountered:
On November 22, 2020 at 10:35:30 AM, Curt Tudor ***@***.***) wrote:
Seeing different behavior depending on which browser is used (with
ziti-sdk-js 0.6.3+)
Although the tmdb web-app test-mule runs very solidly under Chrome
(87.0.4280.67), it intermittently fails under Firefox (83.0) on a Macbook.
The problem manifests on the edge router as:
ERROR [foundation/channel2.(*channelImpl).rxer
[ch{edge}->u{classic}->i{ORXE}] rx error (short read)
The edge router is attempting to read the 4-byte magic number for the
edge-protocol message, but gets zero bytes instead. The error is
unrecoverable on edge router side, so it closes the channel.
The client side then gets confused, and the attempt to decrypt incoming
traffic/responses, manifests an error:
Could not decrypt record or bad MAC
There seems to be some kind of async/timing differences, or websocket
data-chunking differences, concerning how things operate on these two
browsers while running the exact same code.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#31>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AESJOCOFE7I42FWXVJCHS53SREVUFANCNFSM4T6RNK4Q>
.
@smilindave26 No, not in this scenario, because I'm running these tests against a locally-deployed Ziti build/network, that contains realease-next + my-forge-poc stuff.
fwiw, the failure behavior doesn't change if I swap the service from encryption ON or OFF. Always works with Chrome either way, tends to fail with FF either way.
Current evidence suggests that ziti-sdk-js executes slightly differently depending on the browser that is hosting it. i.e. Safari has a slightly different issue which I will open once I have more relevant info.
Seeing different behavior depending on which browser is used (with
ziti-sdk-js
0.6.3+)Although the
tmdb
web-app test-mule runs very solidly underChrome (87.0.4280.67)
, it intermittently fails underFirefox (83.0)
on a Macbook.The problem manifests on the edge router as:
ERROR [foundation/channel2.(*channelImpl).rxer [ch{edge}->u{classic}->i{ORXE}] rx error (short read)
The edge router is attempting to read the 4-byte magic number for the edge-protocol message, but gets zero bytes instead. The error is unrecoverable on edge router side, so it closes the channel.
The client side then gets confused, and the attempt to decrypt incoming traffic/responses, manifests an error:
Could not decrypt record or bad MAC
There seems to be some kind of async/timing differences, or websocket data-chunking differences, concerning how things operate on these two browsers while running the exact same code.
The text was updated successfully, but these errors were encountered: