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 SSO proxy does not handle upstream server-sent events (SSE) / text/event-stream. SSO proxy attempts to handle the request before failing with: ReverseProxy read error during body copy: context deadline exceeded.
A workaround for now is setting a low flush interval:
# upstream_configs.yml
- service: myservice
default:
from: myservice.sso.mydomain.com
to: http://myservice.mynamespace.svc.cluster.local
# HACK: to handle `text/event-stream` (SSE)
# See also: https://github.com/golang/go/issues/27816
options:
flush_interval: 100ms
Load a page that leverages EventSource to receive automatic updates from a "server" behind SSO proxy (in our case, we are proxying https://argoproj.github.io/argo/ UI)
Wait for automatic updates
Check console, and network logs
Request to the server would have timed out
Expected behavior
Any automatic updates (real-time) should be received on the client side.
Screenshots
N/A
Desktop (please complete the following information):
Smartphone (please complete the following information):
N/A
Additional context
We are using buzzfeed/sso:v1.2.0 on Kubernetes 1.13.
The problem is likely related to golang/go#27816. Though, when we recompiled SSO proxy with the latest version of Go (which should have the fix for the linked issue), the problem still persisted.
The text was updated successfully, but these errors were encountered:
Describe the bug
The SSO proxy does not handle upstream server-sent events (SSE) /
text/event-stream
. SSO proxy attempts to handle the request before failing with:ReverseProxy read error during body copy: context deadline exceeded
.A workaround for now is setting a low flush interval:
A potential fix is probably to flush immediately if the content-type matches
text/event-stream
: golang/go@5440bfc#diff-d863507a61be206d112f6e00e6d812a2R342To Reproduce
Steps to reproduce the behavior:
EventSource
to receive automatic updates from a "server" behind SSO proxy (in our case, we are proxying https://argoproj.github.io/argo/ UI)Expected behavior
Any automatic updates (real-time) should be received on the client side.
Screenshots
N/A
Desktop (please complete the following information):
Smartphone (please complete the following information):
N/A
Additional context
We are using
buzzfeed/sso:v1.2.0
on Kubernetes 1.13.The problem is likely related to golang/go#27816. Though, when we recompiled SSO proxy with the latest version of Go (which should have the fix for the linked issue), the problem still persisted.
The text was updated successfully, but these errors were encountered: