If I make a blog post that has the following url: http://www.example.com/checkoutmyguitar&they'reawesome/
I NEED to escape the & or else the & will get processed as an &.
Invalid entities will get ignored, which is what you're seeing. It's the edge cases that are the concern. I think.
Comment
But in that case, the & is in the pathname part of the URL. E.g. http://jsfiddle.net/c5b5L4w1/
So not a problem.
Parent comment
If I make a blog post that has the following url: http://www.example.com/checkoutmyguitar&they'reawesome/ I NEED to escape the & or else the & will get processed as an &. Invalid entities will get ignored, which is what you're seeing. It's the edge cases that are the concern. I think.