Archived Forum Post
Index of archived forum posts
Question:
Archived Forum PostQuestion:
Here is the text from the last error message. It looks like an error 404 but according to the Parse.com documentation the URL is correct and the class does exists and a row with the specified object ID also exists. Any ideas?
ChilkatLog: QuickDeleteStr: DllDate: Dec 12 2012 UnlockPrefix: HAMPDEHttp Username: ROBERTHILLCAAD:bob Architecture: Little Endian; 32-bit Language: .NET 2.0 VerboseLogging: 0 QuickReq: url: https://api.parse.com/1/classes/InspectionSection/Pr4Qvaqy09 QuickGetToOutput_OnExisting: qGet_1: simpleHttpRequest_3: httpMethod: DELETE requestUrl: https://api.parse.com/1/classes/InspectionSection/Pr4Qvaqy09 Connecting to web server... httpServer: api.parse.com port: 443 Using HTTPS. ConnectTimeoutMs_1: 10000 calling ConnectSocket2 IPV6 enabled connect with NO heartbeat. connectingTo: api.parse.com resolveHostname1: dnsCacheLookup: api.parse.com dnsCacheHit: 54.235.204.51 --resolveHostname1 GetHostByNameHB_ipv4: Elapsed time: 0 millisec myIP_1: 192.168.0.218 myPort_1: 65086 connect successful (1) clientHelloMajorMinorVersion: 3.1 buildClientHello: majorVersion: 3 minorVersion: 1 numRandomBytes: 32 essionIdSize: 0 numCipherSuites: 10 numCompressionMethods: 1 --buildClientHello readIncomingTls_serverHello: processTlsRecord: processHandshake: handshakeMessageType: ServerHello handshakeMessageLen: 0x46 processHandshakeMessage: MessageType: ServerHello Processing ServerHello... ServerHello: MajorVersion: 3 MinorVersion: 1 SessionIdLen: 32 CipherSuite: RSA_WITH_AES_256_CBC_SHA CipherSuite: 00,35 CompressionMethod: 0 Queueing ServerHello message. ServerHello is OK. --ServerHello --processHandshakeMessage --processHandshake --processTlsRecord --readIncomingTls_serverHello HandshakeQueue: MessageType: ServerHello --HandshakeQueue Dequeued ServerHello message. readIncomingTls_6: processTlsRecord: processHandshake: handshakeMessageType: Certificate handshakeMessageLen: 0xb96 processHandshakeMessage: MessageType: Certificate ProcessCertificates: Certificate: derSize: 1329 certSubjectCN: *.parse.com certSerial: 0BDD190CC643E4DF6309A67841C43106 CertIssuerCN: DigiCert Hig h Assurance CA-3 --Certificate Certificate: derSize: 1628 certSubjectCN: DigiCert High Assurance CA-3 certSerial: 0A5F114D035B179117D2EFD4038C3F3B certIssuerCN: DigiCert High Assurance EV Root CA --Certificate NumCertificates: 2 Queueing Certificates message... --ProcessCertificates --processHandshakeMessage --processHandshake --processTlsRecord --readIncomingTls_6 Dequeued Certificate message. readIncomingTls_6: processTlsRecord: processHandshake: handshakeMessageType: ServerHelloDone handshakeMessageLen: 0x0 processHandshakeMessage: MessageType: ServerHelloDone Queueing HelloDone message. --processHandshakeMessage --processHandshake --processTlsRecord --readIncomingTls_6 DequeuedMessageType: ServerHelloDone OK to ServerHelloDone! No client certificate required by the server. Encrypted pre-master secret with server certificate RSA public key is OK. Sending ClientKeyExchange... Sent ClientKeyExchange message. Sending ChangeCipherSpec... Sent ChangeCipherSpec message. Derived keys. Installed new outgoing security params. Sending FINISHED message.. algorithm: aes keyLength: 256 Sent FINISHED message.. readIncomingTls_changeCipherSpec2: processTlsRecord: processChangeCipherSpec: ccsProtocolType: 1 --processChangeCipherSpec --processTl sRecord --readIncomingTls_changeCipherSpec2 readIncomingTls_handshakeFinished2: processTlsRecord: processHandshake: handshakeMessageType: HandshakeFinished handshakeMessageLen: 0xc processHandshakeMessage: MessageType: HandshakeFinished FinishedMsgLen: 12 Queueing Finished message. --processHandshakeMessage --processHandshake --processTlsRecord --readIncomingTls_handshakeFinished2 Dequeue the FINISHED message... Dequeued Finished message. Handshake completed successfully. Secure Channel Established. ConnectElapsedMs: 140 -- BuildGetRequest -- Not auto-adding cookies. sendElapsedMs: 0 StatusCode: 404 StatusText: Not Found Reading response body... fetchSslResponseData2_2: No transfer-encoding header field. sslContentLength: 50 extraLen: 50 Already have entire response. --fetchSslResponseData2_2 readResponseElapsedMs: 110 --simpleHttpRequest_3 --qGet_1 --QuickGetToOutput_OnExisting --QuickReq responseSize: 50 responseContentType: application/json; charset=utf-8 DELETE response was binary (not text) --QuickDeleteStr --ChilkatLog
You're using an old version of the library (December 2012), so the first thing I'd try is to update to the latest version and see if it fixes the problem. If not, please post the LastErrorText from the new version (as there may be additional information) in <pre> </pre> tags.
Okay, I updated to the latest version (looks like from May 8) and the error occurs but here's the updated text from LastErrorText.
ChilkatLog: QuickDeleteStr: DllDate: May 8 2014 ChilkatVersion: 9.5.0.39 UnlockPrefix: HAMPDEHttp Username: ROBERTHILLCAAD:bob Architecture: Little Endian; 32-bit Language: .NET 2.0 VerboseLogging: 0 httpRequestStr: a_quickReq: quickHttpRequest: httpVerb: DELETE url: https://api.parse.com/1/classes/InspectionSection/Pr4Qvaqy09 openHttpConnection: Opening connection directly to HTTP server. httpHostname: api.parse.com httpPort: 443 ssl: 1 connect2: connectImplicitSsl: checkServerCert: Not verifying server certificate... Set the RequireSslCertVerify property to true to enable verification. --checkServerCert Secure Channel Established. --connectImplicitSsl --connect2 connectElapsedMs: 234 HTTP connection succeeded. --openHttpConnection buildQuickRequest: genStartLine: startLine: DELETE /1/classes/InspectionSection/Pr4Qvaqy09 HTTP/1.1 --genStartLine addCookies: Not auto-adding cookies. --addCookies --buildQuickRequest sendRequestHeader: sendHeaderElapsedMs: 0 --sendRequestHeader statusCode: 404 statusText: Not Found readResponseBody: contentLength: 50 --readResponseBody --quickHttpRequest --a_quickReq convertResponseBodyToUtf8: responseBodySize: 50 responseContentType: application/json; charset=utf-8 HTTP response body was binary (not text) --convertResponseBodyToUtf8 Returning failed status because of HTTP response code. --httpRequestStr Failed. --QuickDeleteStr --ChilkatLog
The server is responding with 404 - Not Found, which seems to imply that either the class or object that you are try to work against doesn't exist. Maybe the response body has some additional debugging information that might be useful?
Also, I took a quick look at the parse.com API, and it looks like you also need to send your application ID and API key in the HTTP header, are you doing that with the correct ID and key?
This appears to be working now. I'm going to sound like one of my users, but I did not make any changes to the code and I just did some more testing and it is properly removing the objects from Parse.
Wish I know why, but at least it's working!