-
-
Notifications
You must be signed in to change notification settings - Fork 424
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Websockets don't load with capitalized server names #100
Comments
Hi! It's been a little over a week with no response, so I'm just curious what the progress of this is, or if there is even a plan to make non-lowercase server names supported (which in that case you may want to add a warning). Thank you! |
Sorry for that, thanks for reminding about this. When switching between projects I sometime forget about some issues that I wanted to reply to. Actually, For example, Also, capitalized letter can be used in URL paths. For example So all in all, that's why I didn't felt converting automatically name passed using |
That's fine. I understand how you could be so busy with so many repositories. A warning or even a note in the README would be appreciated as I didn't know about this beforehand. |
Name will now automatically be converted to a valid domain to prevent such cases. |
You are very welcome :) |
This time this shouldn't be related to a Windows Insiders build 😀 .
I finally have hotel working by fiddling with the source code a little to suit the weird Windows-related bug, but the websockets on a page I'm proxying don't work when I capitalize the name of a server (but the page still loads).
Otherwise, if the name (which I specify through
hotel add ... -n ...
) is lowercase, the websockets work fine.Looking at the code, the error seems to be in app.js when the server checks to see if the origin is valid. If the name is capitalized, the server id is also capitalized, but the
id
variable (from the origin) is lowercase and therefore does not match, causingservers.has(id)
to returnfalse
.Thanks!
The text was updated successfully, but these errors were encountered: