Aidan Woods 054ba3c487 urlencode urls that are potentially unsafe: ... this should break urls that attempt to include a protocol, or port (these are absolute URLs and should have a whitelisted protocol for use) but URLs that are relative, or relative from the site root should be preserved (though characters non essential for the URL structure may be urlencoded) this approach has significant advantages over attempting to locate something like `javascript:alert(1)` or `javascript:alert(1)` (which are both valid) because browsers have been known to ignore ridiculous characters when encountered (meaning something like `jav\ta\0\0script:alert(1)` would be xss :( ). Instead of trying to chase down a way to interpret a URL to decide whether there is a protocol, this approach ensures that two essential characters needed to achieve a colon are encoded `:` (obviously) and `;` (from `:`). If these characters appear in a relative URL then they are equivalent to their URL encoded form and so this change will be non breaking for that case.		2017-05-03 17:01:27 +01:00
..
data	urlencode urls that are potentially unsafe:	2017-05-03 17:01:27 +01:00
bootstrap.php	attempt to fix failing builds on 5.3	2017-03-29 19:30:24 +03:00
CommonMarkTest.php	attempt to fix failing builds on 5.3	2017-03-29 19:30:24 +03:00
ParsedownTest.php	add xss tests	2017-05-01 03:33:49 +01:00
TestParsedown.php	Use late static binding for Parsedown::instance()	2015-08-13 13:29:33 +03:00