In this article, we will explore everything related to View-source URI scheme in depth. From its historical origins to its relevance today, through its various aspects and applications. View-source URI scheme is a topic of great importance and has aroused the interest of experts and the general public. Along these lines, we will delve into its meaning, impact and evolution over time. Likewise, we will analyze the different perspectives and approaches that have been given, as well as the implications and consequences that it has had in various areas. Read on to discover everything you need to know about View-source URI scheme and its influence on the modern world.
The view-source URI scheme is used by some web browsers to construct URIs that result in the browser displaying the source code of a web page or other web resource.[1]
For example, the URI view-source:https://example.com should show the source of the page located at https://example.com.
In the early Internet, the View Source technique helped people learn by example to create their own web pages.[2]
On 25 May 2011, the 'view-source' URI scheme was officially registered with IANA[3] per RFC 4395.
Firefox and Internet Explorer both supported the scheme, but support was dropped from Internet Explorer in Windows XP SP2 due to security problems.[4] Firefox also suffered a similar security issue (by combining view-source and JavaScript URIs[5]), but still supported it in Firefox 1.5[6] after being fixed. In 2009, a new discovered bug was fixed in Firefox 3.0.9.[7]
| Browser | Supported? |
|---|---|
| Mozilla Firefox | supported[8] |
| SeaMonkey | supported |
| Netscape | supported |
| Internet Explorer 4, 5 and 6 | supported |
| Internet Explorer 6, 7, and 8 | not supported after Windows XP SP2 |
| Safari 3.2.1 | supported |
| Safari 5, 6 | not supported |
| Opera 7, 8, 9, 10, 11 | not supported |
| Opera 15 and up | supported |
| Google Chrome | supported[9] |
| Web | supported |
| HP webOS | via third-party app (Internalz Pro)[10] |