OTAP doesn't work with HTTPS server with some jar-files | Thales IoT Developer Community
December 27, 2019 - 10:56am, 2489 views
Hello,
I have a EHS5 module:
ATI1
Cinterion
EHS5-E
REVISION 03.001
A-REVISION 00.000.14
I have a jar-file which is not downloaded from https server in the otap procedure. The length of that jar-file is: 377148 bytes (maybe it is too big for https?). The otap log is in the enclosed file:
The strange things are:
1. Only HTTPS server doesn't work with this file. When the file is on another HTTP server, everything works fine with the OTAP procedure.
2. Older versions of that jar-file of a smaller size are downloaded without problems by https otap.
What could you advise me to do?
I can provide you with this jar-file if it helps to solve the problem.
Hello,
I just checked it on the same module that you use:
Cinterion
EHS5-E
REVISION 03.001
A-REVISION 00.000.14
and I had no problem to download even bigger (648KB) jar file. I think it can be somehow related to the server configuration. Is there any other HTTPs server that you can test with?
Best regards,
Adam
Hello, Adam,
thank you for your answer.
No, I don't have another HTTPs server.
If I give you a link to the jad-file on my HTTPs-server could you make a test OTAP procedure with your module, is it possible?
Hello,
Please send me the link. I can test it.
As Adam has written the problem may be related to your server. Or maybe it has something to do with the mobile network quality - don't you have any problems with data transmission?
I can see 'Otap timer expired!' in the log. The safety timeout is configured for 20 minutes, so it should be more than enough in normal conditions.
Regards,
Bartłomiej
Hello, Bartłomiej,
here is the link:
https://web.ru/sample_auth/3.3.6/TU41sm.jad
user: sample
password: password
Mobile network quality is ok, CSQ=14.
Update to version 3.3.6 fails, but update to 3.3.5 is ok (replace digit 6 by 5 in the link).
Hello,
I tested both MIDlets with EHS5-E REVISION 03.001 A-REVISION 00.000.14 and got the same behavior as you probably for the newer one. I managed to see the TCP traffic and it looks like the data is being downloaded for a few seconds (around 7) for both cases. And then after the lask data received from the server and last ACK sent by the module:
- for the older MIDlet version: after around 3 seconds the connection is being closed by the module without any further confirmation received from the server.
- for the newer MIDlet version: there is no communication for around 20 minutes and the connection is being closed by the module (FIN, ACK) without any further confirmation received from the server.
It is interesting that for both cases the time of active data transmission was nearly exactly the same (even though the second file was bigger). And then there was nothing untill OTAP timer expired. Have you tried with some other server for reference?
Regards,
Bartłomiej
Hello,
As I understand something is wrong with our HTTPS server. But what is wrong with it?
JAD and JAR files are easyly downloaded by any browser, but not downloaded by EHS5 module..
I think we will eventually use simple HTTP server.
We don't have another HTTPS server (this is customer's server and we can't change it).
Best regars,
Vitaliy
Hello,
Yes, for me it looks like there is something wrong on the server side. It looks as if there was some timer on the server which simply stops replying when it expires. Or there's some other reason but the result is that the module waits but there's no more data from the server. The fact that Adam tested this successfully with our test server (which is a simple Apache server) seems to confirm this.
Best regards,
Bartłomiej