Loading Profile...
Content-type text/xml error?
Hi,
I'm trying to use azigo card selector with the jinfocard.org demo application. I've successfully imported their managed card, but when I try to retrieve values, I get an error. If I examine the error in a protocol debugger, it tells me the request was sent with an unexpected Content-type header (text/xml) whereas it's expecting application/soap+xml; charset=utf-8. Is this a problem with the selector behaviour or with the azigo service? (When I manually change the content-type and re-issue the request, I get a soap response.
Thanks
I'm trying to use azigo card selector with the jinfocard.org demo application. I've successfully imported their managed card, but when I try to retrieve values, I get an error. If I examine the error in a protocol debugger, it tells me the request was sent with an unexpected Content-type header (text/xml) whereas it's expecting application/soap+xml; charset=utf-8. Is this a problem with the selector behaviour or with the azigo service? (When I manually change the content-type and re-issue the request, I get a soap response.
Thanks
I’m frustrated
1
person has this question
I have this question, too!
Tell me when someone answers.
The more people who ask this question, the more it gets noticed.
The more people who ask this question, the more it gets noticed.
Create a customer community for your own organization
Plans starting at $19/month
-
Inappropriate?Hi Peter - we will look into this issue. Initial feedback is we suspect that this is due to the issuing site supporting SOAP 1.2 and the Azigo icard service only supporting SOAP 1.1. This would likely be the cause of the errors you experienced. We are validating this with some testing and will confirm our findings with you.
We do have a udpate for Azigo icard service to support SOAP 1.2 that we are currently testing and planning for our next Azigo service update in coming weeks.
EMPLOYEE
