Bug 1041416 - [RFE][nova]: Spice HTTP proxy
Summary: [RFE][nova]: Spice HTTP proxy
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: RFEs
Version: unspecified
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: 13.0 (Queens)
Assignee: RHOS Maint
QA Contact:
URL: https://blueprints.launchpad.net/nova...
Whiteboard: upstream_milestone_none upstream_stat...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-12-12 16:03 UTC by RHOS Integration
Modified: 2017-07-21 20:08 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-07-21 20:08:32 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description RHOS Integration 2013-12-12 16:03:11 UTC
Cloned from launchpad blueprint https://blueprints.launchpad.net/nova/+spec/spice-http-proxy.

Description:

Provide a custom HTTP proxy to check console token and tunnel traffic from Spice client to Spice server, without using websocket.

Unlike websocket, HTTP proxy tunnels traffic without any transformation. It doesn't handle SSL or stream multiplexing. While websockets are necessary for html client browser integration, they are aliens to native clients, and require non-trivial amount of additional HTTP/websocket support, which provides redundant features (ssl/messaging/multiplexing) over the existing protocols.

HTTP proxy:
- is one of the most common form of tunneling, and some native clients support it for some time
- do not require complex implementation of websockets in client
- do not require transformations of stream on server side, simplifying code, and lowering CPU if handling thousands of sessions

Specification URL (additional information):

None


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