Re: XML RPC - automatically switch to ssl/https if port 443 is specified

Thanks for the 443/SSL fix... I'm pretty sure it has introduced an error. If I run my app on RC2 it works fine, RC5 returns: --------------- Fault Code: 5 Fault Reason: Didn't receive 200 OK from remote server. (HTTP/1.1 400 Bad Request) ---------------- With debug on I get: ---GOT--- HTTP/1.1 400 Bad Request Your browser sent a request that this server could not understand.<P> Client sent malformed Host header<P> I dumped the request operation and it seems to be a problem with the servername in the headers: POST /server.php HTTP/1.0 User-Agent: PEAR XML_RPC Host: ssl://erdfactory.XXXXX.net Authorization: Basic ZnVjazptZQ== Content-Type: text/xml Content-Length: 110 systemLoad ---------- The code added to prefix ssl on the servername if port 443 is selected (that I like) is affecting the request. Also just a quick thought, the code added to prefix the protocol, you might want to pull out into a method, it appears to be completely duplicated for the servername and proxyname, except for the variable that particular operation is being performed on. On Mon, 24 Jan 2005 02:37:43 -0500, Daniel Convissor <danielc@analysisandsolutions.com> wrote: > Hi All: > > Your logic is right on. I modified the behavior a bit and created some > tests for these principles and included them in the latest release, > XML_RPC-1.2.0RC5, which I just rolled out. > > I'd like this to be the last test release before going stable. Please, > test it out and let me know everything works (be it good and/or bad). > > Thanks, > > --Dan > > -- > T H E A N A L Y S I S A N D S O L U T I O N S C O M P A N Y > data intensive web and database programming > http://www.AnalysisAndSolutions.com/ > 4015 7th Ave #4, Brooklyn NY 11232 v: 718-854-0335 f: 718-854-0409 > > -- > PEAR Development Mailing List (http://pear.php.net/) > To unsubscribe, visit: http://www.php.net/unsub.php > >