noVNC process additional data from client
50 views
Skip to first unread message
Kai
Nov 12, 2024, 7:08:48 AM11/12/24
to noVNC
Hello,
I've got a setup with a Docker container and a small X setup inside which provides an application via websockify and NoVNC to a browser. This works quite well for now.
One thing I ran into is opening links inside the container. Whenever I want to open a manual or something, the application wants to open a browser by using "xdg-open".
Of course, there isn't any browser and it should stay as a single-application container.
My plan is to just open this link in a new tab on the client computer which opened noVNC.
I understand that the websockify is the connection between the VNC server and the noVNC client.
My first idea was to modify xdg-open which just takes the link and sends it to noVNC.
I thought about adding an endpoint to websockify, which can be parsed by noVNC and should just open a new tab.
However, I saw that only binary websocket connections are supported and my first idea for a simple HTTP POST didn't work.
Unfortunately I didn't do anything with websockets in the past, so that I don't really have experience.
My question: Did someone already have a similar idea?
Is it a doable thing to add either information to the websocket endpoint or add an HTTP endpoint?
Maybe someone already had this thoughts...
Kai
I've got a setup with a Docker container and a small X setup inside which provides an application via websockify and NoVNC to a browser. This works quite well for now.
One thing I ran into is opening links inside the container. Whenever I want to open a manual or something, the application wants to open a browser by using "xdg-open".
Of course, there isn't any browser and it should stay as a single-application container.
My plan is to just open this link in a new tab on the client computer which opened noVNC.
I understand that the websockify is the connection between the VNC server and the noVNC client.
My first idea was to modify xdg-open which just takes the link and sends it to noVNC.
I thought about adding an endpoint to websockify, which can be parsed by noVNC and should just open a new tab.
However, I saw that only binary websocket connections are supported and my first idea for a simple HTTP POST didn't work.
Unfortunately I didn't do anything with websockets in the past, so that I don't really have experience.
My question: Did someone already have a similar idea?
Is it a doable thing to add either information to the websocket endpoint or add an HTTP endpoint?
Maybe someone already had this thoughts...
Kai
Kai
Jan 8, 2025, 4:51:54 AMJan 8
to noVNC
As I still got it on my list..
Does someone have recommendations to integrate additional messages into the websocket stream in websockify?
I looked in the sources for a while but didn't find a good entry possibility so far..
Thanks!
Pierre Ossman
Jan 15, 2025, 4:14:32 AMJan 15
to no...@googlegroups.com, Kai
On 08/01/2025 10:51, Kai wrote:
> As I still got it on my list..
>
> Does someone have recommendations to integrate additional messages into the
> websocket stream in websockify?
> I looked in the sources for a while but didn't find a good entry
> possibility so far..
>
websockify is designed as a very dumb proxy. So it is likely difficult
> As I still got it on my list..
>
> Does someone have recommendations to integrate additional messages into the
> websocket stream in websockify?
> I looked in the sources for a while but didn't find a good entry
> possibility so far..
>
to add any high level stuff like you want.
When we add new features to noVNC, it is done in the VNC protocol rather
than the communication between noVNC and websockify.
Regards,
--
Pierre Ossman Software Development
Cendio AB https://cendio.com
Teknikringen 8 https://twitter.com/ThinLinc
583 30 Linköping https://facebook.com/ThinLinc
Phone: +46-13-214600
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
Reply all
Reply to author
Forward
0 new messages