Page MenuHomePhabricator

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

Authored by epriestley on Jun 5 2017, 12:48 PM.
Tags
None
Referenced Files
F18853356: D18076.id.diff
Fri, Oct 31, 3:59 PM
F18848854: D18076.diff
Thu, Oct 30, 6:38 AM
F18812295: D18076.diff
Mon, Oct 20, 8:19 AM
F18766807: D18076.id43473.diff
Tue, Oct 7, 6:40 PM
F18760021: D18076.diff
Mon, Oct 6, 7:34 AM
F18759275: D18076.diff
Mon, Oct 6, 2:48 AM
F18752723: D18076.id.diff
Sat, Oct 4, 4:13 PM
F18704264: D18076.diff
Sep 28 2025, 6:49 AM
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