Page MenuHomePhabricator

Don't fatal when encountering [[ <bad URI > | ... ]]
ClosedPublic

Authored by epriestley on Jun 5 2017, 12:48 PM.
Tags
None
Referenced Files
Unknown Object (File)
Tue, Nov 19, 11:00 AM
Unknown Object (File)
Mon, Nov 11, 2:43 AM
Unknown Object (File)
Sat, Nov 9, 1:59 PM
Unknown Object (File)
Sat, Nov 9, 1:59 PM
Unknown Object (File)
Sat, Nov 9, 1:59 PM
Unknown Object (File)
Tue, Nov 5, 11:53 PM
Unknown Object (File)
Oct 25 2024, 5:17 PM
Unknown Object (File)
Oct 15 2024, 3:30 PM
Subscribers
None

Details

Summary

Fixes T12796. In D17647, the parser became more strict, but this remarkup rule doesn't deal with it gracefully.

Instead, detect when the parse failed and bail out.

Test Plan
  • Put [[ http://good.com#u:p@evil.com/ | broken ]] into a Remarkup document without backticks.
  • Before patch: fatal ("rejecting ambiguous URI").
  • After patch: link doesn't work (which is correct), but page does.

Diff Detail

Repository
rPHU libphutil
Lint
Lint Not Applicable
Unit
Tests Not Applicable