Ryan Irelan, the guy behind EE Insider and overall reputable dude has a post summarizing an interesting recent thread (the same one I noted the other day) on his site about our recent move from ExpressionEngine to WordPress on Grist.
Not-very-related aside: What do you notice about the URL for the post:
Hey! A period! Today I noticed that this is illegal in WordPress, though EE permits it. (It’s illegal in WordPress in the sense that requests for URLs with periods [and terminal dashes] are rewritten without those characters.) In any case, this may be either uninteresting or obvious to others, but rfc1738 is more liberal than I thought about what characters can appear unencoded in URLs:
Many URL schemes reserve certain characters for a special meaning:
their appearance in the scheme-specific part of the URL has a
designated semantics. If the character corresponding to an octet is
reserved in a scheme, the octet must be encoded. The characters “;”,
“/”, “?”, “:”, “@”, “=” and “&” are the characters which may be
reserved for special meaning within a scheme. No other characters may
be reserved within a scheme.
Thus, only alphanumerics, the special characters “$-_.+!*’(),”, and
reserved characters used for their reserved purposes may be used
unencoded within a URL.
So neither WP nor EE are wrong in the way they do this!