I don't actually follow the question, but that's because if we're talking POST as in form data, NONE OF THE ABOVE.
I tend to code using the 'one index to rule them all' methodology and as such any page can perform ANY action... creating, deleting, updating, etc, etc, the PATH has not a blasted thing to do with it, the FORM DATA DOES.
which is why client side the only thing you might see in the URI is the comment's # as a on-page link. /post/postname#commentnumber
But in terms of server iteration, this isn't even a thing. This way you cannot risk people creating hotlinks to things like deletion and creation. You HAVE to send postData.
SO many XSS exploits wouldn't even exist if people just showed a little common sense and stopped putting commands and direct links into their URI's.