comparison doc/upgrading.txt @ 4678:23de24f57566

issue2550749 - the xmlrpc interface is invoked on content type and not url path. Sending any text/xml data to roundup results in invoking the xml-rpc interface, but a REST or other interface could also consume xml data and do something different. So require the use of 'http(s)://.../xmlrpc' uri to trigger the xmlrpc interface.
author rouilj
date Sun, 25 Nov 2012 18:24:28 -0500
parents 17197d6145cf
children 24b8011cd2dc
comparison
equal deleted inserted replaced
4677:3cf77c30697e 4678:23de24f57566
21 robots to follow all the links in the calendar. If you haven't modified the 21 robots to follow all the links in the calendar. If you haven't modified the
22 page on your local instance, you can simply replace it with the one in 22 page on your local instance, you can simply replace it with the one in
23 ``share/roundup/templates/classic/html/_generic.calendar.html``; if you did, 23 ``share/roundup/templates/classic/html/_generic.calendar.html``; if you did,
24 you can add the tag manually. See issue2550765 and changeset a099ff2ceff3. 24 you can add the tag manually. See issue2550765 and changeset a099ff2ceff3.
25 25
26 If you are using the xml-rpc interface, there is a change
27 in accessing it. You can not send text/xml data to any
28 roundup url and get a response, you must use the /xmlrpc
29 url. For example, if you used to send your xmlrpc request to:
30
31 http://myroundup.com/roundup
32
33 you need to change the url to read:
34
35 http://myroundup.com/roundup/xmlrpc
36
37 to invoke the xmlrpc handler. This allows us to send xml
38 data to roundup for other handlers (e.g. REST, SOAP ...)
39 in the future.
26 40
27 Migrating from 1.4.19 to 1.4.20 41 Migrating from 1.4.19 to 1.4.20
28 =============================== 42 ===============================
29 43
30 Roundup used to allow certain HTML-Tags in OK- and Error-messages. Since 44 Roundup used to allow certain HTML-Tags in OK- and Error-messages. Since

Roundup Issue Tracker: http://roundup-tracker.org/