protocol handler smoke-tests
Below are checks for protocol handler support defined in IPFS Addressing Spec.
Source: ipfs/in-web-browsers
Clicking on each link should result in the same content loading as HTTP equivalent:
Open diagnostic page at ipfs://bafkreifik2tbj5esf74sf2qwft2x3vuxaqmthwh3d2qx6abpcroirqpt7i
It should self-report an unique Origin based on the URL authority component (baf..), as stated in RFC 2396.
This is prerequisite for secure sandbox provided by same-origin policy
Embedding via<img src="ipfs://QmbWqxBEKC3P8tqsKc98xmWNzrzDtRLMiMPL8wBuTGsMnR" />
..should produce the same result as: <img src="https://ipfs.io/ipfs/QmbWqxBEKC3P8tqsKc98xmWNzrzDtRLMiMPL8wBuTGsMnR" />
Embedding via<video src="ipfs://bafybeigwa5rlpq42cj3arbw27aprhjezhimhqkvhbb2kztjtdxyhjalr3q/big-buck-bunny_trailer.webm#t=5" >
..should produce the same result as:<video src="https://ipfs.io/ipfs/bafybeigwa5rlpq42cj3arbw27aprhjezhimhqkvhbb2kztjtdxyhjalr3q/big-buck-bunny_trailer.webm#t=5" >
Fetching data from ipfs:// via XMLHttpRequest:
..should produce same result as XMLHttpRequest to http:// gateway:
Fetching data from ipfs:// via fetch:
..should produce same result as fetch to a gateway over http://: