[[!meta copyright="Copyright © 2013 Free Software Foundation, Inc."]] [[!meta license="""[[!toggle id="license" text="GFDL 1.2+"]][[!toggleable id="license" text="Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation; with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license is included in the section entitled [[GNU Free Documentation License|/fdl]]."]]"""]] `httpfs` is a virtual filesystem allowing you to access web pages and files. # Source # Documentation ## IRC, freenode, #hurd, 2013-09-03 [[!tag open_issue_documentation]] hi, why I can't cd to /http:/richtlijn.be/~larstiq/hurd/ to do grep? this is not ftp it works for other file ? I can't cd to ~larstiq, I don't know why http is not a filesystem protocol while httpfs could try in representing it as such, it is not something reliable ok, it's not reliable I expect it can expose dir like browser so, the translator just know href from home page, and one by one uh? if ...:80/a/b/c.png exits, but not has a href in homepage, so I can't cd to a, right? you are looking things from the wrong point of view a web server can do anything with URLs, including redirecting, URL rewriting and whatever else so, how to understand httpfs's idea? how httpfs list dir? check its code en, no need it's not reliable it's not work, it's enough I have an idea, for the file system, we explore dir level by level, but for http, we change full path one once time maybe can allow user to cd any directory, and just mark as some special color to make user know the translator was not sure, file exist or not once the file exits, mark all the parent directory as normal color? congzhang: you can find more info about httpfs here: http://nongnu.org/hurdextras/ congzhang: you're still looking at http from the wrong point of view there are no directories nor files you start a request for a URL, and you get some content back (in case there's no error) you mean httpfs just for kidding? that the content is a web page listing a directory on the filesystem of the web server machine, or a file sent back via the connection, or a complex web page, it's the same congzhang: you can only get a list of files if the web server responds with an index of files "files" The readme explains how httpfs does its thing: http://cvs.savannah.gnu.org/viewvc/*checkout*/httpfs/README?root=hurdextras if I can't cd to /http:/host/a/b how to get /http:/host/a/b/c.html, even the file exist? you don't cd in http cd is for changing directory, which does not apply to a protocol like http which is not fs-oriented yes, I agree with you, http was not fs-oriented so httpfs was not so useful You can access the document directly, though, can't you? rekado: I try once more I can't so, the httpfs need some extend, http protocol was not fs oriented, so need some extend to make it work with file system http is not designed for file system usage, so extending it is useless or, httpfs was not so useful there are many other protocols for file systems I don't think so i do if we can't make it more useful, remove it from hurd rep, or extend it more useful add some more rule, to make it work with file system no some paradox in it which paradox? for http vs file system ??? tree oriented and star topology oriented? you don't make any sense