desaintmartin/noVNC — comment on commit acde6784211c33d0ada9905f999ea604525e9600
File:  line 0
By desaintmartin:

I know, I was hesitating to pull-request this thing.

My use case is : in SlapOS, we have some frontend system basically mapping from http://myproxy/kvm1/ to http://[some-ipv6]:6080. We have many instances like this, and the proxy has to be instance-agnostic (i.e not guessing what is in the instance), so vnc static files can not be shared.
So I did this two-minutes change in the code. I can also compute a new URL for client with explicit path parameter, but it was even easier to change noVNC code.

Question is : is it a good thing to implicitly set path? Are there some use case where it can be a problem?