I am getting an unusual amount of errors when posting or checking files. The error is always the same (as below). I examined the session log (will add if requested). The send action is there but there is no response. I am not sure how to investigate further. I think that the timout is expiring sooner than the time listed in the error. Also this may be related, if I pause the app (in vb6 studio) there is 100% chance the error will occur.
ChilkatLog: SynchronousRequest: DllDate: Jan 19 2012 UnlockPrefix: INSURAHttp Username: MATHIS:erik Architecture: Little Endian; 32-bit Language: ActiveX domain: storage101.dfw1.clouddrive.com port: 443 ssl: 1 RequestData: HttpVersion: 1.1 Verb: HEAD Path: /v1/MossoCloudFS_56e9ae2f-a3f9-4d5b-a211-406d4b093bad/eCerts-Archive-2507-2006-12/700166.pdf Charset: utf-8 SendCharset: 0 MimeHeader: Host: storage.clouddrive.com X-Auth-Token: 7952de62-xxxx-yyyy-zzzzzz-a8050b123456 --RequestData ReadTimeout: 20 ConnectTimeout: 10 httpConnect: hostname: storage101.dfw1.clouddrive.com port: 443 ssl: 1 Connected --httpConnect connectTime1: Elapsed time: 0 millisec Not auto-adding cookies. sendRequestTime: Elapsed time: 0 millisec ---- Reading HTTP Response ---- Timeout waiting to read socket or accept connection timeoutMs: 20000 Timed out waiting for incoming SSL/TLS messages. timeoutMs: 20000 Failed to read SSL/TLS application messages. Failed to get response header on SSL connection. Use the SessionLogFilename property to log the HTTP traffic to a file to examime the response. readResponseTime: Elapsed time: 20000 millisec totalTime: Elapsed time: 20000 millisec Failed. --SynchronousRequest --ChilkatLog
asked Jun 08 '12 at 14:41
First, check to see if the problem remains using this new build for the 32-bit HTTP ActiveX: http://www.chilkatsoft.com/preRelease/ChilkatHttp.zip
A typical cause for this kind of problem is when the HTTP request header specifies a Content-Length that is longer than the actual length of the content. Given that you're calling SynchronousRequest, if this is the cause, then it wouldn't be a problem in your application code. If the problem still exists with the new build, then (using the new build) send me the session log in a zipped email attachment. It wouldn't be useful to post the session log here because I need to see the exact bytes without any kind of mangling for forum display purposes..
PS> I forgot to explain why a mismatch between Content-Type header and actual content length would cause the timeout. If the header's Content-Length has a value too large, then the server is stuck waiting for the remainder of the HTTP request it thinks is coming, but it never comes. Meanwhile, the client is waiting for the server's response, which (of course) never arrives..
answered Jun 08 '12 at 18:18
Thanks, it is working now. I will continue to test and update this posting if needed.
answered Jun 08 '12 at 19:09