aMule Forum

English => en_Bugs => Topic started by: Menion on November 17, 2006, 10:22:11 AM

Title: Bad ed2k link parsing (invalid size)
Post by: Menion on November 17, 2006, 10:22:11 AM

Hi guys I'm running amuled SVN 20061103 and there is a serious problem in e2dk link management. I have some linsk that would not be imported for "invalid size". They are files < 400Mb long that are imported correctly with emule. I can post you some examples if you want. Bye!!!

Title: Re: Bad ed2k link parsing (invalid size)
Post by: wuischke on November 17, 2006, 10:26:46 AM

If the files are legally harmless, then please post some.

Title: Re: Bad ed2k link parsing (invalid size)
Post by: Menion on November 17, 2006, 10:34:00 AM

No, they aren't legal  :D I can post some for you in PM. BUT I found that if I import the link in eMule and THEN copy link from eMule tu aMuleGUI (or aMuleWeb) It works ?( !!!!!

Title: Re: Bad ed2k link parsing (invalid size)
Post by: wuischke on November 17, 2006, 07:57:46 PM

Yes, please send me the links via PM, I'm interested in the issue.

Title: Re: Bad ed2k link parsing (invalid size)
Post by: wuischke on November 18, 2006, 01:41:37 PM

Minion sent me some links and pointed the errors out by himself:

When there's a slash in the filename (illegal character) and the link is being processed wrong.
ed2k://|file|name/name|1|d41d8cd98f00b204e9800998ecf8427e|/
The result with aMule is:
name: name
size: name -> thus invalid file size
hash: 1

Without slash everything is being processed fine.
ed2k://|file|namename|1|d41d8cd98f00b204e9800998ecf8427e|/

Through developing amule-emc I know that there's wxToken to be blamed.
Maybe one should filter all slashes except the last character, because this is the only place where it is supposed to be.