jesmrec
commented
3 months ago Those logs do not include http requests, are they enabled?
Open Aitorbp opened 3 months ago
jesmrec
commented
3 months ago Those logs do not include http requests, are they enabled?
Aitorbp
commented
3 months ago Those logs do not include http requests, are they enabled?
No, I will add with http requests enabled
jesmrec
commented
3 months ago Doing some checks about this one. Some inputs:
I think the problem does not depend on the behaviour (copy, remove). It's reproducible with both.
Same with oCIS/oC10. I see same in both. It might be some difference, but, in my quick check, i did not see them.
Not sure if affects, but the failing request is sent with double // just before file name
PUT https://192.168.1.39:9200/dav/spaces/21cac65d-b649-4f97-8d6d-372cb941b147$40d30b7f-276b-45a6-bfdd-cec55bf83436/Bbbbb//PXL_20240819_120404334.jpg
Server answers 409 , that means, server does not expect such input in the request. That error makes sense since the target folder does not exist in remote.
The point here is: why the target folder is re-created in first instance (upload with no error), and not in case of a retry?? answering this will put us in the correct path.
the auto-uploads appear as uploaded correctly, but we have the server off, we don't even have the possibility to press Retry
i don't understand this. If the server is off, uploads never work. Are you sure about this?
Aitorbp
commented
3 months ago Doing some checks about this one. Some inputs:
- I think the problem does not depend on the behaviour (copy, remove). It's reproducible with both.
- Same with oCIS/oC10. I see same in both. It might be some difference, but, in my quick check, i did not see them.
- Not sure if affects, but the failing request is sent with double
//just before file name
PUT https://192.168.1.39:9200/dav/spaces/21cac65d-b649-4f97-8d6d-372cb941b147$40d30b7f-276b-45a6-bfdd-cec55bf83436/Bbbbb//PXL_20240819_120404334.jpg
- Server answers
409, that means, server does not expect such input in the request. That error makes sense since the target folder does not exist in remote.- The point here is: why the target folder is re-created in first instance (upload with no error), and not in case of a retry?? answering this will put us in the correct path.
the auto-uploads appear as uploaded correctly, but we have the server off, we don't even have the possibility to press Retry
i don't understand this. If the server is off, uploads never work. Are you sure about this?
Yes, you are right, I was wrong, because I switched off OCIS server, not OC10. So, because of that I saw the files uploaded.
Actual behaviour
Conflictstatus after aRetry. This behavior occurs when it does not have a destination folder created, which if it does not have one it should create one.Steps to reproduce
removed from original folderbehaviourSteps to reproduce
Result: the auto-uploads appear as uploaded correctly, but we have the server off, we don't even have the possibility to press
Retry. If you turn on the server, nothing changes, those uploads appear uploaded, but you can't find them in the destination folder (it wasn't even created).Expected behaviour
Retry.Can this problem be reproduced with the official owncloud server? (url: https://ocis.ocis.master.owncloud.works, user: einstein, password: relativity)
Environment data
ownCloud app version: 4.3.1
Logs
Android logs:
Log 0C10 when you click on Retry:
Log OCIS behaviour:
Log OCIS behaviour: with http request