[wp-trac] Re: [WordPress Trac] #5804: XML-RPC not handling & in URLs properly.

[WordPress Trac]

#5804: XML-RPC not handling & in URLs properly.
---------------------+------------------------------------------------------
 Reporter:  denney   |        Owner:  anonymous
     Type:  defect   |       Status:  new      
 Priority:  normal   |    Milestone:  2.6      
Component:  XML-RPC  |      Version:  2.3      
 Severity:  normal   |   Resolution:           
 Keywords:           |  
---------------------+------------------------------------------------------
Comment (by darkdragon):

 It is encoding the url, so that XML won't break. It probably would be
 better to use CDATA around the block instead, so that XML doesn't try to
 parse the & as an entity it doesn't understand.

 What IXR is trying to prevent is breaking the parser on the other blog,
 which might not understand what '&' or any other entity means in the
 context of the URL. The XML parser doesn't know that '&' is part of an URL
 and is legal, it just sees an '&' with an illegal entity after it. You
 could then assume that the parser at the other end will crash on the
 XMLRPC, which is a bad thing.

 The other blog should take {{{&}}} and replace them with '&'. Or this
 blog should just encapsulate strings in CDATA blocks. It may or may not
 pose a problem with WordPress, since WordPress doesn't really use an XML
 parser (regex instead) and I'm unsure if IXR is smart enough to understand
 CDATA blocks.

-- 
Ticket URL: <http://trac.wordpress.org/ticket/5804#comment:2>
WordPress Trac <http://trac.wordpress.org/>
WordPress blogging software