Redirects and invalid endpoints

If I've got an endpoint of:

    https://example.com/rpc

What response would you expect if the wrong scheme was used by
mistake?

    http://example.com/rpc

Is there a any one correct answer according to the spec?

A 404 HTTP response with text/html response (ignoring the fact that it
was an XML-RPC request)?

A 302 with a Location: header to the https endpoint?

A 200 response with a fault string?


What do most client libraries do if the HTTP response is not 200?  Will
they not parse the body?  Or does it depend on the content-type of the
response?



-- 
Bill Moseley
[email protected]
Sent from my iMutt


------------------------------------

Yahoo! Groups Links

<*> To visit your group on the web, go to:
    http://groups.yahoo.com/group/xml-rpc/

<*> Your email settings:
    Individual Email | Traditional

<*> To change settings online go to:
    http://groups.yahoo.com/group/xml-rpc/join
    (Yahoo! ID required)

<*> To change settings via email:
    mailto:[email protected] 
    mailto:[email protected]

<*> To unsubscribe from this group, send an email to:
    [email protected]

<*> Your use of Yahoo! Groups is subject to:
    http://docs.yahoo.com/info/terms/