GitLab

feat: bootstrap in dht when the routing table is empty

Otherwise, we could end up with only DHT clients and never re-bootstrap.

I've left the default go-ipfs bootstrapping code in for now as it's technically
possible to disable the DHT entirely.

quic: remove experimental status and add it to the default config

Fixes init output.

But only if private networks are disabled.

Signature verification is now always strict.

chore: update libp2p deps

* Update swarm to prefer QUIC addrs over other addrs.
* Update yamux to increase throughput.

fix: support directory listings even if a 404 page is present

fixes https://github.com/ipfs/go-ipfs/pull/4233#issuecomment-631454543

Basically, there's a trade-off here:

1. We can support directory listings while supporting 404 pages (this PR).
2. If a 404 page is present, directory listings don't work.

Given that option 1 is more flexible and users shouldn't be _too_ confused if
they land on a directory with no index.html page, I've gone with that option.

doc(plugin): document plugin config

test(sharness): fix fuse tests

chore: update deps

And remove use of mafilter library (now rolled into go-multiaddr).

chore: update libp2p

docs: update experimental-features doc with IPNS over pubsub changes.

docs: cleanup config formatting

fix(gateway): ensure directory listings have Content-Type text/html

Files already have an explicit Content-Type set. Be sure to do this for
directory listings as well to avoid a fallback to autodetection in
net/http. That fallback fails when a ResponseWriter is installed that
performs compression.

Report a consistent status code for HEAD requests that end up in a
redirect.

test(sharness): test the local symlink

misc config/experimental-features doc fixes

fix: correctly trim resolved IPNS addresses

fixes https://github.com/ipfs/go-ipfs/issues/7246

Gateway renders pretty 404 pages if available

In the same way that an `index.html` file is rendered, if one is present, when the
requested path is a directory, now an `ipfs-404.html` file is rendered if
the requested file is not present within the specified IPFS object.

`ipfs-404.html` files are looked for in the directory of the requested path and each
parent until one is found, falling back on the well-known 404 error message.

License: MIT
Signed-off-by: JP Hastings-Spital <jphastings@gmail.com>

feat: add a dht stat command

Currently, it just prints out the routing tables.