Error 363507 occurred at LabVIEWHTTPClient.lvlib:GET.vi:390001 - after upgrade to LV2014SP1

[BjarkeDM]

I am using the HTTP-tool to get the body text from a website.

After upgrading LV 2014 to SP1 I now receive:

Error 363507 occurred at LabVIEWHTTPClient.lvlib:GET.vi:390001

Possible reason(s):

LabVIEW: LabVIEW could not verify the authenticity of the server.

Complete call chain:
LabVIEWHTTPClient.lvlib:GET.vi:390001
Test.vi

Before the upgrade this worked with no issues.

My code also works fine on another PC that does not have SP1 (but 2014).

I tried installing the Runtime-Engine 2014 SP1 on a new PC - this also fails with error Error 363507.

What is going on? 

The website I access is a public one, freely available in any browser. So I should not need authentication.
Obviously something changed going to SP1.

---

[mikeporter]

Is this happening with all https sites or just this one. What happens when you try rt o access the same site with Chrome or Firefox? What is the website?

Mike...

[BjarkeDM]

Well from a cursory check most other sites work, but not this one.
Tried a few public sites http and https...
At the moment I can find no other sites that exibits this behavior...

The website:
https://www.politi.dk/da/servicemenu/forside/

Chrome displays the website fine.
Same with IE.

[mikeporter]

Well, I can see the site from here, though some of Google's automatic translation from Danish to English does sound a little ominous, like the story: "Police Control of Easter" -- which is actually a story about the police stepping up DUI drug and alcohol enforcement, not the police controlling Easter.

But on a serious note, I don't see an issue right off, though it does appear to be related to that one site. One more thought, does this happen with all the links on that site? It might be related to this one page.

Mike...

[BjarkeDM]

Hehe - well google translate still needs a bit for work - but all pages on this site exibits this...

[mikeporter]

Come to think of it, 2000 years ago some Roman police did try to control Easter -- and it didn't work...

Mike...

[BjarkeDM]

So what has changed from SP1 and is there a work-around?

[mikeporter]

Now that sounds like a question for NI. From what I have read these client VIs are little more than a wrapper around Windows functions -- so I don't know. Hopefully, a LabVIEW developer will discover this thread.

Mike...

[lhedlund]

Dear all, 

I have looked into this issue and I'm  wondering if anyone can give an example of a site where this behavior appears?

The https://www.politi.dk/da/servicemenu/forside/ site generate the same error for both 2013 and 2014SP1.

The error may be related to the SSL/TLS certificate on the sites. Which means that one need to configure the security of the http client handle.

Regards
Lars

[BjarkeDM]

Thanks for the reply Lars,
It is a frustrating phenomenon as this behavior is only seen in SP1 versions of Labview.

I have not found any other sites where this behavior occurs, albeit I have not searched alot.

Do you have a way of setting up the security of the http client handle as a work-around?

BR.