rejetto forum

Software => HFS ~ HTTP File Server => Topic started by: rejetto on March 10, 2009, 11:40:28 AM

Title: tar problem with latest 2.3
Post by: rejetto on March 10, 2009, 11:40:28 AM
Files inside D produce corrupt .tar of 512k.

this info initially fooled me.
now from the email you sent i can see it's 512 bytes not 512k.
that's actually an empty archive. Winrar says the archive is corrupted, but it's actually not (my pov).
so, the problem, is essentially that no file is put inside the archive, not a file format corruption. focus change.
i will go now on collecting information and trying to fix this problem.
since an empty archive makes little or no sense (and can alert people using winrar) , i was thinking of displaying a page with an error instead of serving it.
opinions?
Title: Re: tar problem with latest 2.3
Post by: Mars on March 10, 2009, 03:01:53 PM
in my archiveperms , when no files were found, the user had a 'no files found'  page, not an empty archive ;)
Title: Re: tar problem with latest 2.3
Post by: SilentPliz on March 10, 2009, 04:31:39 PM
   
To avoid this, it must also that there have not an check box "archive" with the elements of type "links".
Title: Re: tar problem with latest 2.3
Post by: r][m on March 11, 2009, 05:28:16 AM
Quote
i was thinking of displaying a page with an error instead of serving it.

An error page would be nice, I guess, but does that mean archive is not possible below
a certain level subfolder?
Does anyone remember this comming up some time ago? Maybe it was a different
problem with subfolders?
Title: Re: tar problem with latest 2.3
Post by: rejetto on March 11, 2009, 12:40:11 PM
Quote
i was thinking of displaying a page with an error instead of serving it.
An error page would be nice, I guess, but does that mean archive is not possible below
a certain level subfolder?

no, the error page is a different problem, and not truly a bug, just bad design.
please reply my email when you find the time.
Title: Re: tar problem with latest 2.3
Post by: rejetto on March 11, 2009, 12:41:22 PM
in my archiveperms , when no files were found, the user had a 'no files found'  page, not an empty archive ;)

you are using error 404 or what?