Port 443 profile bug in Vault Client

[jtoth]

Hi there,
When I login to Vault Client I set up a profile so that I don't have to re-enter in my vault server/username/password every single time I connect. This works fine if the Vault server is running on any port, except port 443.

When you try to save your profile with vault server: hostname:443 it truncates the :443 and just enters in the vault server as hostname, which fails of course. If you try any other port, even 442 and 444, it works correctly and the vault server is saved with that port #.

It's not a huge issue because you can just type in the port # and click to connect, but it's annoying having to do this every single time you want to connect. It should save this port in the profile...

Is SourceGear going to fix this bug or was this done on purpose?

Thanks,
Justin

[lbauer]

This works fine if the Vault server is running on any port, except port 443

I think this is happenning because 443 is the default port for SSL/HTTPS, just as 80 is the default for HTTP. Vault assumes connections are via port 80 for HTTP or 443 for SSL/HTTPS, so it strips those off as redundant.

If you're connecting to 443 via SSL, then you just need to check the "Use SSL" box in Edit Profiles. If 443 is an HTTP, not HTTPS port, then you're right, the profile won't take it.

I'll log a bug to allow users to have a profile which includes a non-SSL port 443.

[jtoth]

Thanks, we ended up just switching to another port so that the profile would work again.