Hi, there certain types of URLs are not correctly handles, here’s a few I’ve encountered
http://localhost.com/redr/foo -> good
http://localhost:65432/redr/foo -> bad (link address will eventually be replaced by next one below, bug?)
http://localhost:65432/redr/foo.txt -> good
http://localhost:65432/redr/foo.abcde -> bad
http://kinopio.club:443 -> bad (link address will eventually be replaced by next one below, bug?)
https://kinopio.club:443/foo.txt -> good
It seems URLs with port are not handled properly?
1 Like
it looks like that’s because these urls include :ports numbers, I’ll look into adding that. Are you using these for local development?
1 Like
I’m using it to store corporate/intranet pages occasionally, which usually using different ports.
And since Kinopio don’t support custom URI schemes, so I build a local service to support them, eg:
http://localhost:65432/redr/zotero://select/items/0_DZ9FWLSQ
http://localhost:65432/redr/x-devonthink-item://44AF4D11-DBE3-4B6D-BF4C-9CE2D6CAE282
2 Likes
just shipped an update to add http://localhost:123 support , tested w urls above. Should not introduce any regressions with normal url detection but keep your eyes peeled just in case 
3 Likes
