08-19-2010 03:31 PM
I am exploring the possibilities of the new HTTP protocol implementation in LabVIEW 2010.
Doing some debugging with Microsoft network monitor that with every HTTP Init a HTTP Get is sent with the following content:
GET /LVWSAuthSvc/GetAggregateUserPermissions?username= HTTP/1.1..Host: api.imgur.com..Accept: */*....
This is quite strange to me, or am I missing something?
Ton
05-31-2011 09:49 AM
Did you ever get any feedback on this? I am using HTTP Get for an internal application that we are building, and the communication is failing due to this. Is this only designed to work against LabVIEW web services?
Chris
09-05-2011 06:31 AM - last edited on 09-07-2011 04:30 PM by srdfrn
Hello,
If I understand correctly uit what that message means and wrote it below.
The initial line is different for the request than for the response. A
request line has three parts, separated by spaces: a method name, the
local path of the requested resource, and the version of HTTP being used. A
typical request line is:
GET /path/to/file/index.html HTTP/1.0
Notes:
I think that the links below would be useful too.
http://www.jmarshall.com/easy/http/
http://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol
Regards
09-08-2011 10:12 AM - edited 09-08-2011 10:15 AM
Hi Ton (TCPlomp),
My name is Charles and I am the engineer behind the HttpClient.
What you uncovered was a bug in LabVIEW 2010 that we fixed in LabVIEW 2011 (CAR# 288076). In LabVIEW 2010 and LabVIEW 2010SP1, we incorrectly hit the network wire to attempt to log into a webservice, regardless as whether user wished to do this or not. This is not a fatal error and can simply be ignored. Sorry for the confusion.
If you have any additional questions, feel free to ask.
Charles
05-09-2014 03:44 PM
Hi Charles,
I have labview 2010.
I am not particularly interested in upgrading.
I need to make use http post through labview.
I get the same error as described above.
What are my options for getting around this bug?
Is there some sort of patch I can download for this?
11-02-2015 11:54 AM
Hi Charles,
My name is Alejandro,
I have the same problem.
Is there some patch to solve this problem in LabVIEW2010 SP1?. We can't change our LabVIEW developper version at this time
Regards
11-03-2015 04:51 AM
@Alejandro_i wrote:
Hi Charles,
My name is Alejandro,
I have the same problem.
Is there some patch to solve this problem in LabVIEW2010 SP1?. We can't change our LabVIEW developper version at this time
Regards
Did you read his note? "This is not a fatal error and can simply be ignored."
11-03-2015 08:11 AM
Yes, I did.
But we have one customer with this issue: After calling some unavailable method on his WebServer, it avoid any another http request during certain amount of time from the same IP. He tells me the reason is for security policy
Regards
11-03-2015 10:19 AM
Well then you will need to:
a) Get them to make an exception to their security policy
b) Update your software to use a newer version of LabVIEW where the bug is not present
c) Perhaps you could make a firewall rule to block the outgoing request
d) Rewrite the HTTP method using the raw TCP functions
11-04-2015 12:57 AM
Thanks for the info!
We will rewrite HTTP method using TCP functions because we can't change our LabVIEW version
Regards