gateway spec conformance, round 2

[b5]

Building on work in #173, we've covered a lot of the basic requirements for being a spec-compliant gateway. This tracking issue should document what's left.

Spec conformance tests

We need a test for each spec requirement, AND a test for each kubo gateway requirement / deviation. This is going to be a long list of tests. First task is to yank a list of tests to build from the spec itself

• e2e test that confirms UnixFS Directory HTML templates work, render the set of known file extensions, with a working breadcrumb links header

Document our deviations

We also need to test our own "special" behaviours: for example we return a raw block from a link to a CBOR block on the gateway, and use a different HTML template than kubo, these should all be documented.

Remaining Features

Outstanding work to round out gateway support:

• Gateway Subdomain Support #78
• gateway(template): improve 404 handling #253

[Arqu]

This one is still relevant.
#253