Bug 1670289 - Console Login does not work through corporate proxy
Summary: Console Login does not work through corporate proxy
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Management Console
Version: 4.1.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 4.1.0
Assignee: Samuel Padgett
QA Contact: Yadan Pei
URL:
Whiteboard:
Depends On:
Blocks: 1664187
TreeView+ depends on / blocked
 
Reported: 2019-01-29 07:36 UTC by K Chandra Sekar
Modified: 2019-03-13 11:49 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-03-13 11:49:00 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

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?


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