Spice HTTP proxy
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/
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
Blueprint information
- Status:
- Started
- Approver:
- None
- Priority:
- Undefined
- Drafter:
- None
- Direction:
- Needs approval
- Assignee:
- Vladan Popovic
- Definition:
- New
- Series goal:
- None
- Implementation:
-
Needs Code Review
- Milestone target:
- None
- Started by
- elmarco
- Completed by
Related branches
Related bugs
Sprints
Whiteboard
[xqueralt:
Patches are ready for review with spice-http-proxy tag.
Gerrit topic: https:/
Addressed by: https:/
Spice HTTP proxy
Addressed by: https:/
Add spice-http-proxy console type[xqueralt:
Patches are ready for review with spice-http-proxy tag.
Gerrit topic: https:/
Addressed by: https:/
Spice HTTP proxy
Addressed by: https:/
Add spice-http-proxy console type
If you are still working on this, please re-submit via nova-specs. If not, please mark as obsolete, and add a quick comment to describe why. --johnthetubaguy (20th April 2014)
Is there somebody still working on this, I also have a bp about adding a custom HTTP proxy for Ironic shellinabox, maybe it's still worth to add HTTP protocol console types as some drivers can provide web based consoles, https:/
