WebNFS
computer network protocol
YANFS (Yet Another NFS), formerly WebNFS, is an extension to the Network File System (NFS) for allowing clients to access a file system over the internet using a simplified, firewall-friendly protocol.
WebNFS was developed to give Java applets and other internet enabled applications a way of accessing filesystem services over the internet. While NFS provides applications on Unix with full filesystem semantics, not all of these might be needed in a distributed, read-only web environment. Conversely, access restrictions—such as requiring the use of restricted ports for originating requests—normally used in closed environments are not usually applicable in public distributed environments.
In 2007, Sun Microsystems open-sourced its WebNFS implementation. The name was subsequently changed to YANFS (Yet Another NFS) to reflect the expanded scope of the project to include a server-side implementation.
YANFS/WebNFS makes use of a well known port (port 2049 on both UDP and TCP) thus avoiding the overhead and unpredictability of using the ONC RPC portmap protocol. WebNFS adds public filehandles and multicomponent lookups to the NFS protocol.
WebNFS has been specified by a number of RFCs:
RFC 2054: WebNFS Client
RFC 2055: WebNFS Server
RFC 2224: NFS URL Scheme
RFC 2755: Security negotiation for WebNFS
Legacy
While WebNFS itself did not gain much traction, several important WebNFS features later became part of NFSv4, including use of port 2049, and the concept of a fixed "root filehandle" (which evolved from WebNFS public filehandles and allows exported filesystems to be accessed without needing the MOUNT protocol to learn their individual root handles first); both together allow NFSv4 to function without the Portmap service.
“WebNFS” enters the record as computer network protocol. Crown Archives preserves that source wording while asking what WebNFS, computer and network can confirm, complicate or overturn.
Why this record matters
“WebNFS” is worth following because a concise public description often conceals a longer documentary argument. Here, WebNFS, computer and network provides the most credible route into that argument.
Vocabulary and entity names are the principal evidence signals here, because they determine the precision of every later search. The source revision retrieved here is dated Dec 23, 2024. The linked authority identifier is Q7978465. None of the 0 selected statements returned an explicit reference. The first chronological checks are 2007, 2049, 2054 and 2055.
A concise general-reference account can conceal disagreements about scope, terminology or the weight assigned to individual sources. The source lead contains qualifying language; that uncertainty should survive quotation, summary and reuse. Authority statements aid reconciliation but still require their own references, qualifiers and ranks to be checked.
How to read it
Use the entry as an orientation point, then follow its citations and revision history. Names, dates and institutional relationships should be checked against the original record.
- Subject orientation
- Search vocabulary
- Locating named sources
The closest primary source, responsible institution and strongest cited specialist reference.
Three-step research path
- Establish the record: confirm the title “WebNFS”, its source revision and the description used here.
- Expand the search: follow WebNFS primary sources, WebNFS archive and WebNFS research across catalogues and specialist indexes.
- Test the account: compare the strongest cited source with the responsible institution’s current record and note any disagreement.
Questions for further research
- Which source most directly establishes the central claim about “WebNFS”?
- Which institution is responsible for the underlying evidence?
- What terminology or title could unlock a more precise catalogue search?
Search terms from this dossier
This entry incorporates text from “WebNFS” on English Wikipedia. Contributors are listed in the page history. Text is available under the Creative Commons Attribution-ShareAlike 4.0 License. Selected authority identifiers and statements are retrieved from Wikidata under CC0; their references and qualifiers remain part of the verification path.