CID bafkqaaa causes error: cannot detect content-type: EOF

[lidel]

Originally reported by Brave: brave/brave-browser#16671

go-ipfs 0.9.0 updated mimetype dep https://github.com/gabriel-vasile/mimetype and that introduced regression on gateway when an empty byte array payload is returned to the user.

Unfortunately, that edge case changes HTTP response for CID bafkqaaa which we use in various places.

• In v0.8.0 it was empty body with HTTP 200 (ok) status code
• In v0.9.0 it returns cannot detect content-type: EOF with HTTP 500 error

TODO

• Switch back to 1.1.2 (safe choice for patch release) – done: fix: downgrade mimetype dependency #8229

  We were at 1.1.2 in v0.8.0 the latest is v1.3.0 which seems ok, and v1.2.0 is what we have and has the behavior change

• Add sharness tests – done: test: gateway response for bafkqaaa #8232

[aschmahmann]

Switching back to 1.1.2 #8229

[lidel]

Sharness test #8232

[gabriel-vasile]

Hi,

We were at 1.1.2 in v0.8.0 the latest is v1.3.0 which seems ok, and v1.2.0 is what we have and has the behavior change

I'm pretty sure v1.3.0 is not ok. The offending change is gabriel-vasile/mimetype@b1ae8bf#diff-cf06cf150d88adb18fa7da76b698e820f978ae9b6c547b3530305051e6687459L44
I'll add the missing err != io.EOF and release it as v.1.3.1.

[gabriel-vasile]

v1.3.1 is out and it behaves like 1.1.2.
the change