WBN
(Web Bundle)
Entry created on 2019-09-10 02:08:11 ( 5 years ago ) Last updated on 2023-02-13 01:32:36 ( 2 years ago )
Bundled HTTP Exchanges represent a collection of HTTP exchanges. An HTTP exchange is a pair of HTTP request/response. It can include signatures with the semantics of Signed HTTP Exchanges, or not.
This feature allows Chrome to navigate into Bundled HTTP Exchanges, i.e. browser can navigate into a page whose entire resources (including main and sub resources) are bundled in a Bundled Exchange. It is expected to enable easy sharing and offline browsing of a web site.
What is a WBN file? A WBN file is a website saved as a single file. It contains all of the website's content, including webpages, images, fonts, scripts, and other assets. The WBN format was created by the Web Incubator Community Group (WICG).
More Information Screenshot of a .wbn file in Web Archive Browsing Advanced Client WBN file open in Web Archive Browsing Advanced Client In the interest of making websites and web apps easier to share and open offline, developers within WICG, an offshoot of the World Wide Web Consotrium (W3C), created the WBN format. Saving a website in the WBN format packages all that website's files into a single file, which a user can then share over Bluetooth, Wi-Fi, or a local network. Theoretically, other users can then open the WBN file in their web browser to access the website it contains, without connecting to the Internet.
Each WBN file is a renamed Concise Binary Object Representation (CBOR) file, which uses the .wbn extension instead of the .cbor extension. CBOR files are similar to .JSON files, except they store data primarily in a binary format, rather than as plain text.
NOTE: Google removed Chrome's support for WBN files in February 2023. It is possible that Google may restore Chrome's support for WBN files in the future.
Web Bundle Web Bundles are a WebPlatform.org incubating proposal for a collection of http resources, each of which can be signed or unsigned.[11] Web bundles can be directly loaded by Chrome/Chromium if enabled[12] and displayed the same as if they had been loaded directly over http.
