Multi Commander > Support and Feedback

Cloud Drives

<< < (4/5) > >>

Mathias (Author):
Well.. Im not sure that is incorrect..

GrantSP:
Ok. that got me thinking. So I went the other way.

If I take the actual path and "encode" it, this is the result:

QzpcVXNlcnNcR3JhbnRcRHJvcGJveA==

Now if I take the path as decoded from the hosts.db and then encode it, this is the result:

QzpcVXNlcnNcR3JhbnRcRHJvcGJveA8=

Clearly they are not the same. As you say, there are extra bytes added somewhere/somehow.
Am the only user that has this problem with DropBox? Maybe no-one else uses it?

DropBox is not taking into account the special character. Unicode instead of ascii? Wrong, or missing, byte-order marker maybe?

I am going to update the report to DropBox at any rate as it appears to be a problem with them.

Mathias (Author):
I think it is very unlikely that DropBox is doing anything wrong.
The base64 text is correct.  both of them..
And it is not an unicode issue then nothing would have worked.

Must be some decoding issue with the base64 decoding library I use. It is some third part code that I use, I have not written it my self. But it has not been change so strange that it worked before..

GrantSP:
Very well, I trust your judgement.

I guess I must be the only one with a DropBox account!

Thank you.

Mathias (Author):
hehe no you are not..

But I looks like it is because of your name, the way the path is encoded (you name are in the path) make the decode mess up the last character and say that there are 1 character more then there is. So I think it is some decoder issue that only get trigger in some situations depending on the content it decodes.
So there is some problem with the decoder.

Navigation

[0] Message Index

[#] Next page

[*] Previous page