This is not the first time that this blog was requested for incorrect URLs:
Someone kindly shared my post about pipes.sh, unfortunately, there is a stinking closing parenthesis ()) attached to the end of URL, which causes the 404 error. Lucky for me, I was aware of any 404 errors.
But the problem is whoever visited through the incorrect link might just close the tab and never got to see the post they were originally sent to. I had been wanting to resolve this kind of situation, so visitors would have chance to get to the post.
I implemented very simple workaround, now the page would give you a search link, which is generated off the incorrect link:
1 Don’t wrap link with anything tight but spaces
I have seen many ways, (), <>, **, or []. There are all problematic, 404-prone. If you are going to wrap a link, at least put a space as the safeguard measure.
In many cases, once your message with the link is out, you can only delete it and re-post. But in most cases, the posters don’t even know they make a mistake, and nobody cares to poke the posters. Not like they fix the link by themselves, but simply think it’s just another 404 link of content being taken down, which is not.
If you want to say: that’s stupid to think ) is part of URL. One name for you: Wikipedia.
Put a GDS (GodDamn Space) after your fraking link!
0 comments:
Post a Comment
Note: Only a member of this blog may post a comment.