If you are implementing a REST service, then I agree with you 100%. WebRPC is simply a different interpretation. In WebRPC, GET means "get the result of executing this method". POST basically means the same thing, but the arguments are passed in the message body (just like an HTML form).

The client libraries all use POST internally - GET is primarily useful for testing and debugging (so you can easily execute a method in the browser).

If you're transferring anything other than hypertext over http then you're a hypocrite.