Content-Type is broken #68

Closed
opened 2025-12-28 18:14:03 +00:00 by sami · 0 comments
Owner

Originally created by @roman-khimov on GitHub (Feb 4, 2025).

Originally assigned to: @mike-petrov on GitHub.

Current Behavior

send.fs.neo.org is broken.

Expected Behavior

It MUST work.

Possible Solution

Fix it.

Please also split type checks from upload (two loops are ok).

Steps to Reproduce

Try uploading anything.

Regression

Yes. 7b7801ff86 changes Content-Type for non-binary objects to be "". Now binaries can be uploaded, OK, but any regular files can't be. It's a grave regression.

Your Environment

  • Version of the product used: 0.6.3
Originally created by @roman-khimov on GitHub (Feb 4, 2025). Originally assigned to: @mike-petrov on GitHub. ## Current Behavior send.fs.neo.org is broken. ## Expected Behavior It MUST work. ## Possible Solution Fix it. Please also split type checks from upload (two loops are ok). ## Steps to Reproduce Try uploading anything. ## Regression Yes. 7b7801ff8645465f8d0edf5267f548e61da45b1c changes Content-Type for non-binary objects to be "". Now binaries can be uploaded, OK, but any regular files can't be. It's a grave regression. ## Your Environment * Version of the product used: 0.6.3
sami 2025-12-28 18:14:03 +00:00
  • closed this issue
  • added the
    bug
    S4
    I4
    U0
    labels
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
nspcc-dev/send-fs-neo-org#68
No description provided.