Closed josephmturner closed 1 year ago
This is happening because I haven't added code which throws an error if there's no peers/data found yet.
I consolidated the invalid URL tests into one, which tests for invalid domains and z32 public keys.
Is this still necessary?
Is this still necessary?
Yes, I think so.
This is happening because I haven't added code which throws an error if there's no peers/data found yet.
I think we still want hypercore-fetch to return an error when there are no peers for a hyperdrive, right?
I just tried loading a "fake" valid z32 encoded url with the latest hyper-gateway, and I got status 200 with ETag 1. Is that expected?
I rebased off master. Looks like this is still an issue.
My only worry is that invalid public keys can be useful for extension messages. But I think I can special case that for the $/extensions
subpath.
This request should fail, but it doesn't.