divelogs.de: parsing response on upload

Lubomir I. Ivanov neolit123 at gmail.com
Sat Dec 7 09:56:51 UTC 2013

On 7 December 2013 19:22, Rainer Mohr <mail at divelogs.de> wrote:
> Gentlemen,
> Am 07.12.13 16:35, schrieb Dirk Hohndel:
> and the transfer is reported as successful, but then this is the
> server response:
> <?xml version="1.0" encoding="UTF-8"?>
> <divelogsDataImport version="1.0">
>   <Login>succeeded</Login>
>   <FileCopy>failed</FileCopy> <---------------- ?
>   <entered>0</entered>
>   <skipped>0</skipped>
>   <profiles>0</profiles>
> </divelogsDataImport>
> and the uploaded dive is missing in the web interface.
> any ideas?
> FileCopy failed is the response you get when no DLD File has been POSTed to
> the API. Ist the fieldname of the POSTed File "userfile"?
> So to me it looks like there was no file transmitted.

yes it is.

and a byte stream definitely reaches the Qt method here:

i've also tried:
- re-arranging the parts to be "user", "pass", "userfile", as they are
"userfile", "user", "pass" currently
- using QHttpPart::setBody() instead of QHttpPart::setBodyDevice()
but that does not seem to help.

i'm adding a CC to thiago to see if he has an idea why this happens.


More information about the subsurface mailing list