rejetto forum

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - marribi

Pages: 1
1
HFS ~ HTTP File Server / Re: New version: 2.3m
« on: August 22, 2018, 12:18:00 PM »
Nice work rejetto, thank you.

2
HFS ~ HTTP File Server / Re: Download limits
« on: October 17, 2017, 08:48:11 AM »
Just tryed some simple thing:
Code: [Select]
[download]
{.if|{.%item-size-kb% > 4000000.}|Sorry, limit of 4Gb.}

But it seems its not working, i can download file of 5.3GB
May be i need to enable some option ?

3
HFS ~ HTTP File Server / Re: Download limits
« on: October 12, 2017, 09:34:53 AM »
Was looking for solution to restrict user to download, lets say more then 5Gb in 24h and found this old thread.
If anyone can help, how to change this code:

Code: [Select]
[download]
{.if| {. {.sub| {.time|y.} | {.^#limit_%ip%_time.} /sub.} > 1 .}
  |{: {.set|#limit_%ip%_downloads | 100.} :}
  |{:
  {.if|{. {.^#limit_%ip%_downloads.} > 0 |{: {.dec|#limit_%ip%_downloads.}  :}
      |{: {.disconnection reason | downloading too much .} :}
  .}
:}
.}

To account limit? Or where i can read what variables hfs can use ?
And last question where it should be ? i havent found in HFS gui some scripts section ?


4
HFS ~ HTTP File Server / Re: HFS freezes on upload.
« on: October 09, 2017, 06:47:57 AM »
hi! is the browser uploading from your same LAN ?

Hello rejetto !

No, user upload file from different LAN (WAN).
Connection is simple, user -> dns -> router firewall+nat -> vm windows with HFS
HFS have real folders (red folders) path is dfs unc path.
I also tryed with antivirus and without (on clean Server 2016 machine).
Different browsers ie/edge/google chrome.
I configured test HFS on my home lab server and it works normaly, just uploaded 1.5 gb file w/o freeze or lag.
May be on my main HFS server there some old configuration options that interrupt normal operation but how to find it.

5
HFS ~ HTTP File Server / HFS freezes on upload.
« on: October 05, 2017, 12:11:27 PM »
Hello to everyone!

I have strange bug, when someone upload big file to my HFS it becomes unstable while uploading.
Admin interface not responding, web interface cannot display page, but when upload finishes everything became back to normal again.
I tryed different operating systems, windows 7, 2008R2, 2016.
And different templates, standart, rywy, salaf.
Also 2 different hfs versions 2.3i and 2.3k.
But no luck.
Anyone got something like this ? any ideas what to do ?

6
I still don't understand your question. If you use "OEM file names for tar archives" does it work? If you don't use that option, does it work? Which option works best?...

Я все еще не понимаю Ваш вопрос. Если вы используете "OEM file names for tar archives", она работает? Если Вы не используете эту опцию, она работает? Какой вариант лучше работает?...

Hello LeoNeeson !
My question is about that i cant get normally working encoding for Cyrillic letters for both winrar and 7-zip.
If i download files from HFS using download all files from this folder, HFS makes tar archive.

And if i check option "OEM file names for tar archives"
7-zip 16.01 unzip contents normally, but WinRaR broke file names encoding.

If i uncheck option "OEM file names for tar archives"
WinRaR unzip contents normally, but 7-zip 16.01  broke file names encoding.

Like i show on screenshots.

I just got answer from WinRaR tech support.

Quote
Last years tar archives tend to use UTF-8 encoding for file names.

WinRAR, beginning from version 5.40, attempts to use UTF-8 for tar first. If conversion from UTF-8 fails, WinRAR switches to ANSI encoding, which is CP1251 for Russian.

As far as I know, 7-Zip also attempts to use UTF-8 for tar first.
If conversion from UTF-8 fails, 7-Zip switches to OEM encoding, which is CP866 for Russian.

There is no reliable way to detect the file name encoding in TAR, so both WinRAR and 7-Zip just take a wild guess. This time the archive was in CP866 encoding, so 7-Zip guess was correct. In case of ANSI encoding WinRAR guess would be correct. Both would be correct for UTF-8 encoding.

Beginning from WinRAR 5.40 it is possible to override the code page selected by WinRAR and specify another code page. Open this archive in WinRAR first, then open "Options/Name encoding" WinRAR menu and select "866 (OEM - Russian)". Then browse or unpack the archive.
This name encoding menu is not available in WinRAR 5.20.

If they are right its better to code names in HFS tar archives in UTF-8, and problem will be solved !

7
Hello everyone !
Any new suggestions ?
I wrote to winrar support, no answer as well.

8
i'm slightly confused, are these files that were downloaded form HFS?, as what you described is an issues with the zip archive program not reading the file correctly, and i would recommend a md5 check of the file.
Yes this files were downloaded from same HFS server, md5 is ok.

Only difference between this 2 files that they were downloaded with and without option "OEM file names for tar archives".

9
Добрый день всем !
Знаю что на форуме уже есть подобный вопрос, но ответы не совсем совпадают с тем что хотелось бы реализовать.

Собственно ситуация:
Если скачивать папку с файлами в названии которых есть кириллица, с установленной галочкой "OEM file names for tar archives".
То при открытии с помощью WinRaR кодировка имен нарушена (рис.1), но при открытии с помощью 7-zip 16.01 все нормально(рис.2).

Если скачивать папку с файлами в названии которых есть кириллица, сняв галочку "OEM file names for tar archives".
То при открытии с помощью WinRaR все нормально (рис.3), но при открытии с помощью 7-zip 16.01 кодировка нарушена (рис.4).

Собственно можно ли как то сделать что бы при открытии любым из этих архиваторов кириллица отображалась нормально ?

Pages: 1