Customer is unable to open a pop-up when connected to a backend hosted on OpenShift 4.11.28
Connection path:
client --> firewall --> loadbalancer --> Haproxy --> backend --> database

client connection to backend works fine, can browse hosted webpage, and is able to consistently query data from the database without being disconnected. We are able to remain linked to the webpage and navigate around, pulling data from the database consistently as well (there is no networking breakdown that I can detect in an extended test from client --> pod --> database) and tcpcaptures show that data is recieved by the pod successfully as well.

When we click a minor button within the application, the pod issues a request to the database and returns a 200 (internally in the pod log) that the data was acqiured. It then tries to establish a connection to the client in a new pop-up window, and IN THIS WINDOW, we see a 502 bad gateway response. The client is unable to negotiate back to the pod and re-link to the ongoing session stream when handled by haproxy.

We are unable to replicate this behavior when we use nodeport; this only occurs when we route through haproxy.

We tested with:
- 1 haproxy instance (router-default) pod
- 1 backend pod

The issue does not appear to be in how the traffic is passed to haproxy via loadbalancer either as a result, since there was only 1 backend available on a subsequent test that had the same issue.

OCP 4.11.28

every time

1. deploy test application that deploys a pop-up window
2. click the pop-up generating weblink and observe new window is created that is unable to pipe traffic to the backend to retrieve information pulled from database *only observable when using a route*
3. Observe cannot replicate when using nodeport to connect to service and open up pop-ups.

interupted browsing experience

haproxy should be able to handle a pop-up

case details and logs available in next update below.