-
-
Notifications
You must be signed in to change notification settings - Fork 3.2k
Gateway: client opt-in JSON responses for directory listing #7552
Copy link
Copy link
Open
Labels
P3Low: Not priority right nowLow: Not priority right noweffort/daysEstimated to take multiple days, but less than a weekEstimated to take multiple days, but less than a weekexp/intermediatePrior experience is likely helpfulPrior experience is likely helpfulhelp wantedSeeking public contribution on this issueSeeking public contribution on this issuekind/enhancementA net-new feature or improvement to an existing featureA net-new feature or improvement to an existing featurekind/featureA new featureA new featurestatus/readyReady to be workedReady to be workedtopic/gatewayTopic gatewayTopic gateway
Description
Metadata
Metadata
Assignees
Labels
P3Low: Not priority right nowLow: Not priority right noweffort/daysEstimated to take multiple days, but less than a weekEstimated to take multiple days, but less than a weekexp/intermediatePrior experience is likely helpfulPrior experience is likely helpfulhelp wantedSeeking public contribution on this issueSeeking public contribution on this issuekind/enhancementA net-new feature or improvement to an existing featureA net-new feature or improvement to an existing featurekind/featureA new featureA new featurestatus/readyReady to be workedReady to be workedtopic/gatewayTopic gatewayTopic gateway
Followup to #7431, that was closed but had the valuable feature of accessing json manifest of folder
requests to a "folder", especially the root of a folder published to ipns such as http://bafzbeibxww7y6v5metkgmxeqkvls74uqvptbhommrb5b7xianigcicdvuy.ipns.localhost/
should be served the same response as
https://ipfs.io/api/v0/ls?arg=bafzbeibxww7y6v5metkgmxeqkvls74uqvptbhommrb5b7xianigcicdvuy
IF the accept content type header is set to "application/json" that way there is no interference with existing gateway behaviour and with serving the index.html file at the root