Hello,
IF we swti6ch to Vault, I will use vault in two ways. First, ionternally through a local URL, naturally, but second by publishing it to the web y port forwarding. This will allow ecxternal developers to use the service without exstablishing a VPN JUST for this, and SSL is good enough.
As a result, there will be two host-names (an internal one, an external one) that will be used to access the vault service.
Now, the VaultService default page (accesible through /VauldService) for some reason I do not understand, has (actually some) issues in our setup.
It basically always (even if called externally) shows the internal host name in it's links - not wanted, not needed. Why are the hyperlinks not created by using the called host header?
Another issue, btw - ou have severe problems with localization. See, the page says my copy was installed 19 M?rz 2005. German locale. It should read 19 März 2005.
VaultService default page has link error.
Moderator: SourceGear
Re: VaultService default page has link error.
Looks like a bug.THONA wrote:Why are the hyperlinks not created by using the called host header?
This one too.THONA wrote:It should read 19 März 2005.
Thanks for the report.
Eric Sink
Software Craftsman
SourceGear
Software Craftsman
SourceGear