Cannot upload jar file #3497

@PedroAS7 commented on GitHub (Aug 8, 2019):

application/java-archive not working on Gitea 1.9.0 either

@PedroAS7 commented on GitHub (Aug 8, 2019): _application/java-archive_ not working on Gitea 1.9.0 either

GiteaMirror commented

@tomposmiko commented on GitHub (Aug 16, 2019):

What is the severity of this issue from your perspective?

@tomposmiko commented on GitHub (Aug 16, 2019): What is the severity of this issue from your perspective?

GiteaMirror commented

@lunny commented on GitHub (Aug 16, 2019):

Where did you upload? Releases or issues?

@lunny commented on GitHub (Aug 16, 2019): Where did you upload? Releases or issues?

GiteaMirror commented

@lunny commented on GitHub (Aug 16, 2019):

There are two allowed_types, you may changed the wrong section. I uploaded successfully on my local instance both the releases and issues.

[repository.upload]
ALLOWED_TYPES = "application/zip|application/gzip|application/x-gzip|application/x-gtar|application/x-tgz|application/x-compressed-tar|application/java-archive"

[attachment]
ALLOWED_TYPES = "application/zip|application/gzip|application/x-gzip|application/x-gtar|application/x-tgz|application/x-compressed-tar|application/java-archive"

@lunny commented on GitHub (Aug 16, 2019): There are two allowed_types, you may changed the wrong section. I uploaded successfully on my local instance both the releases and issues. ```ini [repository.upload] ALLOWED_TYPES = "application/zip|application/gzip|application/x-gzip|application/x-gtar|application/x-tgz|application/x-compressed-tar|application/java-archive" [attachment] ALLOWED_TYPES = "application/zip|application/gzip|application/x-gzip|application/x-gtar|application/x-tgz|application/x-compressed-tar|application/java-archive" ```

GiteaMirror commented

@tomposmiko commented on GitHub (Aug 16, 2019):

Where did you upload? Releases or issues?

releases

@tomposmiko commented on GitHub (Aug 16, 2019): > Where did you upload? Releases or issues? releases

GiteaMirror commented

@tomposmiko commented on GitHub (Aug 23, 2019):

Hmm, this is interesting.

$ mkdir -p data/tmp/uploads
$ chown ...
$ service gitea restart

And it starts working.
However, after second restart, it stops working, because the tmp directory is gone!
In fact I investigated the following scenarios:

no [repsitory.upload] section in app.ini
-> no success, even if the directory is created.

[repository.upload]
ENABLED = true
TEMP_PATH = data/tmp/uploads
FILE_MAX_SIZE = 3
MAX_FILES = 5
ALLOWED_TYPES = image/jpeg|image/png|application/zip|application/gzip|application/java-archive

It works after first service restart if the directory is created. It does not work after the second restart, the tmp directory is gone.

[repository.upload]
ENABLED = true
TEMP_PATH = /data/gitea/data/tmp/uploads
FILE_MAX_SIZE = 3
MAX_FILES = 5
ALLOWED_TYPES = image/jpeg|image/png|application/zip|application/gzip|application/java-archive

Directory created, service restarted.
No success

TEMP_PATH = tmp/uploads
Directory created, service restarted.
No success

So I got lost, I have no idea

@tomposmiko commented on GitHub (Aug 23, 2019): Hmm, this is interesting. $ mkdir -p data/tmp/uploads $ chown ... $ service gitea restart And it starts working. However, after second restart, it stops working, because the tmp directory is gone! In fact I investigated the following scenarios: 1. no [repsitory.upload] section in app.ini -> no success, even if the directory is created. 2. [repository.upload] ENABLED = true TEMP_PATH = data/tmp/uploads FILE_MAX_SIZE = 3 MAX_FILES = 5 ALLOWED_TYPES = image/jpeg|image/png|application/zip|application/gzip|application/java-archive It works after first service restart if the directory is created. It does not work after the second restart, the tmp directory is gone. 3. [repository.upload] ENABLED = true TEMP_PATH = /data/gitea/data/tmp/uploads FILE_MAX_SIZE = 3 MAX_FILES = 5 ALLOWED_TYPES = image/jpeg|image/png|application/zip|application/gzip|application/java-archive Directory created, service restarted. No success 4. TEMP_PATH = tmp/uploads Directory created, service restarted. No success So I got lost, I have no idea

GiteaMirror commented

@lafriks commented on GitHub (Aug 24, 2019):

You should try mount tmp as volume in docker

@lafriks commented on GitHub (Aug 24, 2019): You should try mount tmp as volume in docker

GiteaMirror commented

@tomposmiko commented on GitHub (Aug 24, 2019):

I don't use docker.

@tomposmiko commented on GitHub (Aug 24, 2019): I don't use docker.

GiteaMirror commented

@tomposmiko commented on GitHub (Aug 27, 2019):

Hmm, this is interesting.

$ mkdir -p data/tmp/uploads
$ chown ...
$ service gitea restart

And it starts working.
However, after second restart, it stops working, because the tmp directory is gone!
In fact I investigated the following scenarios:

no [repsitory.upload] section in app.ini
-> no success, even if the directory is created.

[repository.upload]
ENABLED = true
TEMP_PATH = data/tmp/uploads
FILE_MAX_SIZE = 3
MAX_FILES = 5
ALLOWED_TYPES = image/jpeg|image/png|application/zip|application/gzip|application/java-archive

It works after first service restart if the directory is created. It does not work after the second restart, the tmp directory is gone.

[repository.upload]
ENABLED = true
TEMP_PATH = /data/gitea/data/tmp/uploads
FILE_MAX_SIZE = 3
MAX_FILES = 5
ALLOWED_TYPES = image/jpeg|image/png|application/zip|application/gzip|application/java-archive

Directory created, service restarted.
No success

TEMP_PATH = tmp/uploads
Directory created, service restarted.
No success

So I got lost, I have no idea

@tomposmiko commented on GitHub (Aug 27, 2019): Hmm, this is interesting. $ mkdir -p data/tmp/uploads $ chown ... $ service gitea restart And it starts working. However, after second restart, it stops working, because the tmp directory is gone! In fact I investigated the following scenarios: 1. no [repsitory.upload] section in app.ini -> no success, even if the directory is created. 2. [repository.upload] ENABLED = true TEMP_PATH = data/tmp/uploads FILE_MAX_SIZE = 3 MAX_FILES = 5 ALLOWED_TYPES = image/jpeg|image/png|application/zip|application/gzip|application/java-archive It works after first service restart if the directory is created. It does not work after the second restart, the tmp directory is gone. 3. [repository.upload] ENABLED = true TEMP_PATH = /data/gitea/data/tmp/uploads FILE_MAX_SIZE = 3 MAX_FILES = 5 ALLOWED_TYPES = image/jpeg|image/png|application/zip|application/gzip|application/java-archive Directory created, service restarted. No success 4. TEMP_PATH = tmp/uploads Directory created, service restarted. No success So I got lost, I have no idea

GiteaMirror commented

@tomposmiko commented on GitHub (Aug 27, 2019):

Is it a bug or do I miss something?

@tomposmiko commented on GitHub (Aug 27, 2019): Is it a bug or do I miss something?

GiteaMirror commented

@sapk commented on GitHub (Aug 28, 2019):

Gitea should support upload of java archive so it must be a configuration or system problem.
To be able to debug, do you have any log of the failed upload ?

@sapk commented on GitHub (Aug 28, 2019): Gitea should support upload of java archive so it must be a configuration or system problem. To be able to debug, do you have any log of the failed upload ?

GiteaMirror commented

@stale[bot] commented on GitHub (Oct 27, 2019):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.

@stale[bot] commented on GitHub (Oct 27, 2019): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.

GiteaMirror commented

@reikjarloekl commented on GitHub (Jan 14, 2020):

I have the same issue but with .zip files. Can be reproduced on try.giteo.io using a Windows 10 PC and Chrome or Firefox.
It works using iOS! So apparently, mime type is set differently/ incorrectly using Windows 10/ Chrome or Firefox?

2020-01-14 21_09_59-Release aktualisieren - test - Gitea_ Git with a cup of tea - https___try gitea

@reikjarloekl commented on GitHub (Jan 14, 2020): I have the same issue but with .zip files. Can be reproduced on try.giteo.io using a Windows 10 PC and Chrome or Firefox. It works using iOS! So apparently, mime type is set differently/ incorrectly using Windows 10/ Chrome or Firefox? <img width="398" alt="2020-01-14 21_09_59-Release aktualisieren - test - Gitea_ Git with a cup of tea - https___try gitea" src="https://user-images.githubusercontent.com/839540/72378750-500a1b00-3712-11ea-963e-4505d245a26e.png">

GiteaMirror commented

@sapk commented on GitHub (Jan 14, 2020):

Yes, It is possible that browser/os use different value. You can debug the mime type in gitea log or with the network inspector on firefox and chrome.
For Chrome: https://developers.google.com/web/tools/chrome-devtools/network#load

@sapk commented on GitHub (Jan 14, 2020): Yes, It is possible that browser/os use different value. You can debug the mime type in gitea log or with the network inspector on firefox and chrome. For Chrome: https://developers.google.com/web/tools/chrome-devtools/network#load

GiteaMirror commented

@reikjarloekl commented on GitHub (Jan 14, 2020):

There is no activity in the network tab. Possibly the javascript is already blocking the file from being uploaded?

@reikjarloekl commented on GitHub (Jan 14, 2020): There is no activity in the network tab. Possibly the javascript is already blocking the file from being uploaded?

GiteaMirror commented