search

microsoft / vsts-extension-multivalue-control

A work item form control which allows selection of multiple values.
MIT License
47 stars 45 forks source link

Can't load the control when using multiple web fronts through load balancer #28

Closed ghost closed 5 years ago

ghost commented 7 years ago

I have to web fronts, let's say web1.foo.com and web2.foo.com, they are behind a load balancer tfs.foo.com and their dns is not exposed publicly for security purpose.

When the control tries to load, it fails given this information message:

GET https://web1.foo.com/_apis/public/gallery/publisher/ms-devlabs/extension/vsts-extensions-multivalue-control/1.0.6/assetbyname/dist/index.html net::ERR_NAME_NOT_RESOLVED

My understanding is the Javascript code should use tfs.foo.com instead of the dns name of the machine that is currently serving the custom control's server code.

mmanela commented 7 years ago

@nockawa What is the public access url you set for TFS in the config management application?

ghost commented 7 years ago

tfs.foo.com is set as the public URL in the TFS Administration console.

slumley1 commented 7 years ago

@nockawa What version of TFS are you running?

ghost commented 7 years ago

2017.2

slumley1 commented 7 years ago

@nockawa would it be possible to look at the iis logs on either of the backends to see what the cs_host field is coming in as?

ghost commented 7 years ago

Ok, as a temporary fix we added publicly the web1.foo.com and web1.foo.com pointing to their respective servers and now the request is no longer asking for either web1 or web2 but tfs.foo.com... Definitely weird!

Your code is now requesting the right URL because we've just added the DNS entries of the web frontends...

Any clue?

mmanela commented 6 years ago

@nockawa Do you still have an issue?

ostreifel commented 5 years ago

Closing this issue due to inactivity.