Bug 1670289

Summary:	Console Login does not work through corporate proxy
Product:	OpenShift Container Platform	Reporter:	K Chandra Sekar <csekar>
Component:	Management Console	Assignee:	Samuel Padgett <spadgett>
Status:	CLOSED NOTABUG	QA Contact:	Yadan Pei <yapei>
Severity:	high	Docs Contact:
Priority:	high
Version:	4.1.0	CC:	aos-bugs, csekar, erich, jokerman, mmccomas, pweil
Target Milestone:	---
Target Release:	4.1.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-03-13 11:49:00 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1664187

Description K Chandra Sekar 2019-01-29 07:36:12 UTC

Description of problem:
Using my corporate laptop to connect to my openshift instance via web ( https://console-openshift-console.apps.dev.xxx.xxx ) the certificate error gets displayed (internal certificate) but afterwards the page does not get displayed. 

The DeveloperTools show the following error in the console:
Failed to load resource: net::ERR_INVALID_CHUNKED_ENCODING
for https://console-openshift-console.apps.dev.xxx.xxx/static/vendors~main-chunk-d49ce91e5d088ed46e11.min.js

the exclusive opening of https://console-openshift-console.apps.dev.xxx.xx/static/vendors~main-chunk-d49ce91e5d088ed46e11.min.js does work

Version-Release number of selected component (if applicable):

Actual results:

Web-Console is not visible when accessed via proxy.


Expected results:

Web-Console should be visible when accessed via proxy also

Additional info:

Coporate Environment with SSL-Intercepting proxy and IDS/IPS and AV-Scanning on that Proxy.
Behaviour is identical when using Chrome or IE (Using Windows 7)

This behavior does NOT exist in an non-proxy environment using Windows 10 and Firefox Quantum 64

Comment 1 Samuel Padgett 2019-01-29 14:23:00 UTC

It sounds like the proxy is keeping the `Transfer-Encoding: Chunked` response header from the original response, but not actually serving the content as chunks. If this is the case, it's not a problem in the console and would need to be fixed in the proxy itself. Are you able to reach out to your corporate IT department to help troubleshoot?