xml-rpc-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 14272] New: - Secure functionality is poorly documented, and difficult to get working.
Date Tue, 05 Nov 2002 20:36:11 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=14272>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=14272

Secure functionality is poorly documented, and difficult to get working.

           Summary: Secure functionality is poorly documented, and difficult
                    to get working.
           Product: XML-RPC
           Version: unspecified
          Platform: All
        OS/Version: Other
            Status: NEW
          Severity: Major
          Priority: Other
         Component: Source
        AssignedTo: rpc-dev@xml.apache.org
        ReportedBy: m.redington@ucl.ac.uk


Secure functionality (e.g. using the SecureWebServer and SecureXMLRPCClient classes is poorly
documented, and very difficult for a naive user to get to work correctly.

The non-obviousness of the correct approach is illustrated by the failure of queries to rpc-users
on how to get the attached sample code to work to generate any response.

Mime
View raw message