Skip to content
This repository has been archived by the owner on Mar 4, 2021. It is now read-only.

[feature request] default content-type value #38

Open
lovasoa opened this issue Mar 20, 2020 · 3 comments
Open

[feature request] default content-type value #38

lovasoa opened this issue Mar 20, 2020 · 3 comments

Comments

@lovasoa
Copy link

lovasoa commented Mar 20, 2020

It would be nice if the content-type were not mandatory, using application/octet-stream as a default value. This is the content-type to use for data of an unknown/unspecified type.

@ranisalt
Copy link

Why not be even better and detect content type? That's how csexton/release-asset-action works.

@eine
Copy link

eine commented Mar 21, 2020

Possible dup of #7.

@lazyfrosch
Copy link

I'd use application/octet-stream, it is a safe default to push a file 1:1 binary wise. Avoids complexity and should work for everyone.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants