Need help with old app accessing https URL
Several years ago a developer in Seattle set up a cloud service for me and enhanced my vb.net program so it could access the service at http://argonsvc1.cloudapp.net/facade/scanner.svc. This vb.net app runs on older Symbol scanners using Windows CE and Compact Framework compiled using Visual Studio 2008, since we can't use any version more current than 2008.
Fast forward to now, where the developer has set up a new server for our new Android apps, while intending to make it possible for this older app to also access this new server as https://facade.argonservices.com/Scanner.svc. If I simply change the Web Reference URL in my code to this, it compiles fine, but won't connect with the service. He thinks it's because I'm having to now use a https connection vs. the old http.
The developer does not know how to fix this problem--which is why I need help here at e-e. He did make a few suggestions as follows in the conversation below--most of which I don't understand:
~~~~~~~~~~~~~~~~~~~~~~~~~~
It could be that the legacy code is configured to only connect to non-secure/encrypted channels on that service call.
Odds are you need to alter the service binding to allow for a secure channel.
He then told me to look for references to "BasicHTTP" and the conversation continued as follows:
There are about five points in the program that include “BasicHttp”, such as the one below. Does this mean I can manually change those to “BasicHttps” and expect it possibly solve the problem? For example:
System.Web.Services.WebSer
No.
That would likely crash the whole darn thing and possibly prevent compiling.
You need to first look at the definition Scanner class which is created in the code. Might be just as easy to update the service reference binding with the new address and tell it to do an update of the service reference.
~~~~~~~~~~~~~~~~~~~~~~~~~~
I have NO idea how to do what he is saying, and he won't help because the code is so old. Does anyone here have knowledge of how I would go about making this work, i.e. accessing this new https URL? TIA
Fast forward to now, where the developer has set up a new server for our new Android apps, while intending to make it possible for this older app to also access this new server as https://facade.argonservices.com/Scanner.svc. If I simply change the Web Reference URL in my code to this, it compiles fine, but won't connect with the service. He thinks it's because I'm having to now use a https connection vs. the old http.
The developer does not know how to fix this problem--which is why I need help here at e-e. He did make a few suggestions as follows in the conversation below--most of which I don't understand:
~~~~~~~~~~~~~~~~~~~~~~~~~~
It could be that the legacy code is configured to only connect to non-secure/encrypted channels on that service call.
Odds are you need to alter the service binding to allow for a secure channel.
He then told me to look for references to "BasicHTTP" and the conversation continued as follows:
There are about five points in the program that include “BasicHttp”, such as the one below. Does this mean I can manually change those to “BasicHttps” and expect it possibly solve the problem? For example:
System.Web.Services.WebSer
No.
That would likely crash the whole darn thing and possibly prevent compiling.
You need to first look at the definition Scanner class which is created in the code. Might be just as easy to update the service reference binding with the new address and tell it to do an update of the service reference.
~~~~~~~~~~~~~~~~~~~~~~~~~~
I have NO idea how to do what he is saying, and he won't help because the code is so old. Does anyone here have knowledge of how I would go about making this work, i.e. accessing this new https URL? TIA
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
argonservices.com is not a registered domain
ASKER
I did not spell out the "real" URL from a privacy and security standpoint, since our cloud service maintains data for about 50 clients, and I was assuming it would not be necessary for the purpose of getting guidance on how to change from a http connection to an https. But if that IS required for this discussion, someone tell me. One thing for sure is that my old http URL is registered and working as is my new https URL.
Open in new window
Your service must have a working IP to begin debugging what might be wrong.