() Artur Malabarba <bruce.connor.am@gmail.com>
() Wed, 21 Jan 2015 23:14:56 -0200

   I'll see if I can find out where this happens in url.el.
   If not, I'll just file a bug report.  IMHO, the package
   should either support both versions indiscriminately, or
   warn the user if they use the wrong version.

This is not a legitimate complaint.  HTTP specifies the
all-upcase spelling explicitly, so url.el DTRT already.
(Nod to pedants: Actually, RFC1945 sez "The method is
case-sensitive." and lists "POST" in the RHS in the
‘Method’ non-terminal production...)

If anything, a bug-report is indicated for the server side:
unrecognized method names should ellicit status code 501
(error; "not implemented").

   Even better (as Sean suggests) would be to support and
   encourage the use of symbols.

This is a separate issue, but legitimate.  Personally, i'd love
to see more symbols and fewer strings-as-symbols, all around.
(Insert rant on languages lacking a "symbol" data type, here.)

-- 
Thien-Thi Nguyen
   GPG key: 4C807502
   (if you're human and you know it)
      read my lisp: (responsep (questions 'technical)
                               (not (via 'mailing-list)))
                     => nil