this.url in reference pointing to http: instead of https:

[Tim Reynolds]

We use CSS in our staging environment to load balance calls to our web
services. However, when adding a web reference to a basic C# .Net windows
app, the wsdl & reference.cs generated both point to http: instead of https:.

our CSS is https://vose.ebiz.verizon.com/voseapp/Tpv.axms?wsdl

When adding this reference, the wsdl generated shows:
<port name="TPVSoap" binding="s0:TPV Soap">
<soap:address location="http://vose.ebiz.veriz on.com/voseapp/Tpv.asmx"
/>
</port>
<port name="TPVHttpGe t" binding="s0:TPV HttpGet">
<http:address location="http://vose.ebiz.veriz on.com/voseapp/Tpv.asmx"
/>
</port>
<port name="TPVHttpPo st" binding="s0:TPV HttpPost">
<http:address location="http://vose.ebiz.veriz on.com/voseapp/Tpv.asmx"
/>
</port>

and the corresponding reference.cs shows:
this.Url = "http://vose.ebiz.veriz on.com/voseapp/Tpv.asmx";

When trying to run the windows app and call a web service at this location
it throws an expection - System.Net.WebE xception: The operation has timed-out.

However, when I manually modify the reference.cs as
this.Url = "https://vose.ebiz.veriz on.com/voseapp/Tpv.asmx";

it works fine - web service is executed and data returned.

Additionally, I can call the webservice directly, passing all the parms in
the url:

https://vose.ebiz.verizon.com/voseapp/Tpv.asmx/GetTPVOrder?BillingTN=123456789&OrderNumber=&RepID=v121119

and this works -

However, when I try to test the web service using IE browser - (from
https://vose.ebiz.verizon.com/voseap...op=GetTPVOrder) and press
Invoke button - the new browser window comes up without the 's' (just http)
and it clocks and clocks till finally page not found.

So my suspicion is that the WSDL is incorrect in not showing the 's' (just
using http), but am not sure why.

Please help.
thanks, Tim

[Tim Reynolds]

RE: this.url in reference pointing to http: instead of https:

Microsoft,
Do you still gurantantee the 2day response in these managed news groups from
MSDN universal subscription holders? I am just wondering b/c another post of
mine recevied no response and I am a holder, plus this one will be 2 days old
shortly.
Please advise...

"Tim Reynolds" wrote:
[color=blue]
> We use CSS in our staging environment to load balance calls to our web
> services. However, when adding a web reference to a basic C# .Net windows
> app, the wsdl & reference.cs generated both point to http: instead of https:.
>
> our CSS is https://vose.ebiz.verizon.com/voseapp/Tpv.axms?wsdl
>
> When adding this reference, the wsdl generated shows:
> <port name="TPVSoap" binding="s0:TPV Soap">
> <soap:address location="http://vose.ebiz.veriz on.com/voseapp/Tpv.asmx"
> />
> </port>
> <port name="TPVHttpGe t" binding="s0:TPV HttpGet">
> <http:address location="http://vose.ebiz.veriz on.com/voseapp/Tpv.asmx"
> />
> </port>
> <port name="TPVHttpPo st" binding="s0:TPV HttpPost">
> <http:address location="http://vose.ebiz.veriz on.com/voseapp/Tpv.asmx"
> />
> </port>
>
> and the corresponding reference.cs shows:
> this.Url = "http://vose.ebiz.veriz on.com/voseapp/Tpv.asmx";
>
> When trying to run the windows app and call a web service at this location
> it throws an expection - System.Net.WebE xception: The operation has timed-out.
>
> However, when I manually modify the reference.cs as
> this.Url = "https://vose.ebiz.veriz on.com/voseapp/Tpv.asmx";
>
> it works fine - web service is executed and data returned.
>
> Additionally, I can call the webservice directly, passing all the parms in
> the url:
> https://vose.ebiz.verizon.com/voseap...&RepID=v121119
>
> and this works -
>
> However, when I try to test the web service using IE browser - (from
> https://vose.ebiz.verizon.com/voseap...op=GetTPVOrder) and press
> Invoke button - the new browser window comes up without the 's' (just http)
> and it clocks and clocks till finally page not found.
>
> So my suspicion is that the WSDL is incorrect in not showing the 's' (just
> using http), but am not sure why.
>
> Please help.
> thanks, Tim[/color]