描述
Checklist
- My issue is specific & actionable.
- I am not suggesting a protocol enhancement.
- I have searched on the issue tracker for my issue.
Description
Is your feature request related to a problem? Please describe.
Right now the web interface is served from the node. There is an /webui/ endpoint but it just redirects to the CID such as /ipfs/bafybeic4gops3d3lyrisqku37uio33nvt6fqxvkxihrwlqsuvf76yln4fm/. This is quite annoying as it means that pages don't have stable URLs. I would like to be able to use bookmarks and my browser's history to pages such as specific directories in my MFS repo. Right now the link will pin an older version and navigating using the /webui/ path will pollute my history with different but equivalent URLs.
As the W3C says Cool URIs don't change.
Describe the solution you'd like
Instead of redirecting the webui would just serve the page from the /webui/ endpoint.
This may cause some minor issues with caching as the webui uses relative URLs. However this is probably fine since a brief look shows that they contain content hashes in the filenames anyways so they should still be cachable forever (as long as the index page has a reasonable timeout). In fact this may improve caching as assets that are unchanged between versions will keep the same URL.
An alternative solution to caching would be to still load the assets from /ipfs/{cid}/... but that would require updating the webui itself which may be more work for no gain.