4 ms·
> Make sure the link starts with 'https://www.who.int' https://www.who.int' This should include a trailing slash, otherwise something like 'https://www.who.int
by hk__2 7y ago
> Make sure the link starts with 'https://www.who.int' https://www.who.int'
This should include a trailing slash, otherwise something like 'https://www.who.int.example.com' https://www.who.int.example.com' qualifies as “starts with 'https://www.who.int https://www.who.int '”.
Edit: strangely, if I try to edit my comment above to remove the space between .int and ', HN serves me a 502 Bad Gateway.
- deleted 7y ago[deleted]
- deleted 7y ago[deleted]
- deleted 7y ago[deleted]
- srl 7y ago--I'm writing this comment because I want to see if I can reproduce that bug.-- Well, I give up. Whether or not I get the error appears to not only depend on the text I'm trying to change to, but also the text I'm changing from. It does look like HN is trying to parse the URL, and is unhappy with a URL that ends with the three characters <'".>. But the weird hysteresis... I can't guess. (How on earth am I supposed to quote a string like <'".>?)
- jchw 7y ago> (How on earth am I supposed to quote a string like <'".>?) Well, obviously... "'\"." :)
- microcolonel 7y agoHN/arc markdown link parsing is super broken, doesn't terminate with > either, which causes all sorts of confusion.
- colanderman 7y agoContext: < > is one of the two mechanisms suggested by the URI RFC [1] for delimiting plaintext URIs (the other being " "). [1] https://tools.ietf.org/html/rfc3986#appendix-C https://tools.ietf.org/html/rfc3986#appendix-C