Bug 1573487 - IE11 and Console CORS problem
Summary: IE11 and Console CORS problem
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Management Console
Version: 3.9.0
Hardware: Unspecified
OS: Unspecified
medium
low
Target Milestone: ---
: 4.1.0
Assignee: Samuel Padgett
QA Contact: Yadan Pei
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-05-01 13:40 UTC by Eric Paris
Modified: 2019-06-04 20:12 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-06-04 20:12:36 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Eric Paris 2018-05-01 13:40:34 UTC
Today openshift adds the console/api TLS cert onto the amazon ELB which fronts the console/api machines. I'm told (through the grapevine which no one really knows the truth of) that this is because of some "IE11 CORS bug." But I know little else.

It might be this issue:
https://developer.microsoft.com/en-us/microsoft-edge/platform/issues/1282036/
(It might not, I really don't know)

I would like to stop loading the cert into the ELB. This makes cert management much harder. If this can be fixed in the console I would very strongly like to fix it there.

Comment 3 Samuel Padgett 2019-06-04 20:12:36 UTC
This is no longer an issue in 4.1 since the console uses a proxy and does not rely on CORS. We've also dropped support for IE 11 in 4.1. We have no plan to change this in the 3.x console.


Note You need to log in before you can comment on or make changes to this bug.