yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #11985
[Bug 1228649] Re: noVNC doesn't work when offloaded to port 80 or 443
Too late for Grizzly, final stable/grizzly 2013.1.5 has been released.
** Tags removed: grizzly-backport-potential
** Also affects: nova/grizzly
Importance: Undecided
Status: New
** Changed in: nova/grizzly
Status: New => Won't Fix
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1228649
Title:
noVNC doesn't work when offloaded to port 80 or 443
Status in OpenStack Compute (Nova):
Invalid
Status in OpenStack Compute (nova) grizzly series:
Won't Fix
Status in “nova” package in Ubuntu:
Fix Released
Status in “nova” source package in Raring:
Triaged
Bug description:
When offloading nova-novnc to port 80 or 443 the javascript code does
not load the websockets code properly, and the page simply shows
"Loading" in black text.
The problem is due to the javascript using `window.location.port`
which parses the browser's address bar. This is always an empty
string when the protocol is http or https.
The noVNC project addressed this issue in the following patches.
https://github.com/kanaka/noVNC/pull/245
https://github.com/kanaka/noVNC/pull/252
Would like to request a newer nova-novnc be built, or patch the
existing package with the PR above, and backport to grizzly's UEC
ppas.
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1228649/+subscriptions