Created by: Anthony Palomba on 04-11-2010 09:51:08 PM We have been testing our c20 here with TC4.0.0.234394Beta8. One thing I have noticed is that HTTP posts seem to be handled differently now.
Basically, whenever I post an XML command via the HTTP XML API, I get an http response 500 (server error).
Previous versions of firmware (TC3.1.2) do not have this problem. I am curious as to what may have changed in this version.
Does anyone know if there were any changes made to the way the c-series handles HTTP posts? Are there any release notes that came with TC4.0.0.234394Beta8?
Subject: RE: Strange HTTP API behavior with TC4.0 beta Replied by: Viggo Fredriksen on 05-11-2010 03:10:35 PM Hi Anthony,
could you please supply an example of a failing POST and I'll do some more investigation.
Thanks, Viggo
Subject: RE: Strange HTTP API behavior with TC4.0 beta Replied by: Anthony Palomba on 05-11-2010 04:24:14 PM Any XML command will fail. For example this command should return local phonebook entries...
I am making the request from iOS4. The url I construct is "http://192.168.1.51/formputxml". The body of the HTTP POST contains the XML of the command.
It appears that something has changed in the way these messages are handled because TC3.1.2 seems to work fine. Also, it looks like Xpath commands do not return any results.
Subject: RE: Strange HTTP API behavior with TC4.0 beta Replied by: Anthony Palomba on 10-11-2010 05:28:38 PM Is there an update on the status of this issue?
Subject: RE: Strange HTTP API behavior with TC4.0 beta Replied by: Viggo Fredriksen on 11-11-2010 11:17:38 AM We've spent some time trying to figure this one out. We've been unable to reproduce it, but the following steps may give some more clues.
1) Does Advanced Configuration work in the web interface? 2) Does a re-upgrade of the codec software fix the problem?
If re-upgrading of the codec does not fix the problem, could you supply us with a wireshark log of the interaction between your application and the codec?
If re-upgrading fixes the problem, please post it here.
Thanks, Viggo
Subject: RE: Strange HTTP API behavior with TC4.0 beta Replied by: Anthony Palomba on 11-11-2010 05:17:23 PM Are you doing your testing in Mac or Windows environment? I can easily reproduced the problem with the iPhone app vControl. It allows you to remotely control TANDBERG endpoints with your iPhone/iPad. http://itunes.apple.com/us/app/vcontrol/id335038194?mt=8
This app works fine in with TC3.1.2, but does not work with TC4.0.
1) Does Advanced Configuration work in the web interface?
Most settings work, for example MainVideoSource works, but AllowWebSnapshots does not.
2) Does a re-upgrade of the codec software fix the problem?
We have not tried reinstalling TC4.0.0.234394Beta8, I believe it is not possible to install the same patch using the same release key.
I will try to get a wire shark trace of the HTTP traffic.
Anthony
Subject: RE: Strange HTTP API behavior with TC4.0 beta Replied by: Viggo Fredriksen on 11-11-2010 05:50:45 PM You should be able to upgrade the software again using the same release key. I've tried to reproduce with Windows and Linux.
If I read your report correctly, it seems you're already POSTing xml in the body of the request. Could you try to rewrite from formputxml to putxml just to see if that works?
With putxml there's no need to supply the xmldoc argument in the URI (while formputxml really shouldn't care about the HTTP body).
Regards, Viggo
Subject: RE: Strange HTTP API behavior with TC4.0 beta Replied by: Anthony Palomba on 11-11-2010 06:28:40 PM I modified the code so that it sends a POST with the following URI: http://192.168.1.51/putxml The body of the POST contains the same command as before.
The codec returns a status 400 (Bad Request).
Subject: RE: Strange HTTP API behavior with TC4.0 beta Replied by: Viggo Fredriksen on 11-11-2010 07:11:26 PM Okey -- I think we need to have the http wireshark logs (or similar) in order to get any further on this issue.
Subject: RE: Strange HTTP API behavior with TC4.0 beta Replied by: Anthony Palomba on 11-11-2010 09:38:39 PM You should easily be able to test this be using the vControl iPhone app.
I should have a Wireshark trace shortly...
Subject: RE: Strange HTTP API behavior with TC4.0 beta Replied by: Anthony Palomba on 11-11-2010 10:14:05 PM Viggo, do you have an email address that I can send this trace to?
Alternately, you are welcome to send me a message at anthony dot palomba at vyopta dot com
Thanks again for your help in debugging this issue.
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community:
