Avaya IP Office Web Self Admin IE11 issue

[SirTechalot]

Hi All.
I have done quite a lot of trolling on internet and this forum, but have not found anyone else with this issue. It is about that time when you start to think you are imagining the problem, but here it is anyway.
I have an interesting issue with the Avaya IP Office Web Self Admin feature added in R9.1. It would appear that Internet Explorer has a problem with this when a proxy server is configured (either real or bogus test proxy). The page loads past the HTTPS security warning, but never actually displays the log on window - the page stays blank.
https://[AvayaIPO]:7070/WebManagement/selfadmin.html
As soon as the proxy is removed, the page works again.
Chrome and Forefox have no problem which is interesting as they use exactly the same proxy settings by default.
Avaya have indicated that this is an IE problem, which I agree with, but the problem is that with a good deal of the corporate world using a proxy and a bigger percentage using IE, the clients will see IE11 (in this case, but all versions I have tested appear to do the same) as not being compatible with Avaya IP Office.
It is possible that there is some tweaking to IEs default settings that I have missed - I have tried a few.
Are there any IE gurus out there that have alarm bells ringing in their head about this one?
Thanks in advance.

 

[sizbut]

In the IE settings for the proxy server address you can set exception addresses and there is also the "Bypass proxy server for local addresses" setting.

Stuck in a never ending cycle of file copying.

 

[SirTechalot]

Thanks. Yes the client has a general exception added with a subnet wildcard - ie 192.168.76.*
Other internally resolved URLs and IPs work fine which proves the exception is OK, but the IPO web page is still a problem.
I have spoken to another client with this issue who has got around the issue by putting an exception for the IPO IP address in the proxy server itself.
As mentioned, Chrome and Firefox are OK, so this issue only with IE. Maybe a timing thing?
Perhaps exception in proxy is only way to fix.

Cheers.

 

[intrigrant]

Check the registry for these keys:
[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Internet Settings]
"ProxyEnable"=dword:00000001
"ProxyServer"="10.1.1.12:8080"
"ProxyOverride"="

http://*.internal.lan;https://*.internal.com;<local

This is a example, values may differ for the last two keys.

 

[SirTechalot]

Thanks Intrigrant.
In my testing I have checked that the registry keys reflect the correct values indicating that the proxy has configured correctly.
My test scenario uses 1.1.1.1:8080 as proxy server (obviously bogus) and exception of 192.168.14.* (LAN subnet)
"ProxyEnable"=dword:00000001
"ProxyServer"="1.1.1.1:8080"
"ProxyOverride"="192.168.14.*;<local>"
Internet addresses fail (as you would expect) and internal IPs etc are OK (except test IPO Web Self Admin)
I thought perhaps syntax was a problem, but even in it's simplest form of 192.168.14.* or the actual IPO IP address directly, the IPO web page has issues in IE.
Chrome works fine which uses same proxy settings thus proving proxy syntax is OK.
A very strange one.