Hi,
Just trying to get into Freenet index I got this message and was asked
to forward it to the developers, so here it is:
Erreur interne : merci de prévenir les développeurs
java.lang.NoSuchMethodError: java.lang.String.isEmpty()Z
at
I wanted to ask something, I think it is related : Do you see, sometime when
downloading a file (like a .zip or .png for example) fproxy telling you that
the file is .zip.bin or .png.bin with an unknown mime type ?
Can someone try with this file please ? It's a new one, I had it from fms..
On Thu, Oct 29, 2009 at 6:51 AM, henri godron enjoy...@gmail.com wrote:
I wanted to ask something, I think it is related : Do you see, sometime when
downloading a file (like a .zip or .png for example) fproxy telling you that
the file is .zip.bin or .png.bin with an unknown mime type ?
Can
Hi everyone,
I splitted a file into many .rar files and there is something strange in the
mime type decetion when inserting the files in my node.
Most of them are being re-compressed (because their mime type is not
detected as being a compressed file) and some others are being recognized
As far as I know the node uses the file extension to guess the file type.
You said you compressed into many rar files, what are the file extensions?
Is it possible that the node guesses .rar files correctly, but fails
with .r00, .r01, ... ?
This would explain what you see...
On Tue, Oct 27,
All the files where .rar files.
Example : daemon4304-lite.part103.rar
That's why it is weird...
On Tue, Oct 27, 2009 at 11:30 AM, bbac...@googlemail.com wrote:
As far as I know the node uses the file extension to guess the file type.
You said you compressed into many rar files, what are the
henri godron пишет:
All the files where .rar files.
Example : daemon4304-lite.part103.rar
That's why it is weird...
I found that every so often when the computer is busy the node keeps the
default
mime for the file even when there is clearly identifiable or specified mime
type. Try
Ok, I knew all of that but I was just testing. Btw thanks for reminding me
:)
To keep on the initial problem, I looked at the source code and it seems
that yes, we look at the file extensions to know the mime type. So there is
a bug somewhere about that. I don't know exactly where, when I have
