You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@ws.apache.org by Phil Wilson <ph...@philwilson.org> on 2004/01/09 15:20:19 UTC

Modifying HTTP request headers

Hi all,

A project I'm working on uses the salesforce.com web services[1]. In 
order to use their XML-RPC interface I need to be able to specify the 
content of the "Cookie" HTTP request header (the value of which is 
specified by the return from an initial login).

Is there any way of doing this in the 1.1 release? I know that towards 
the end of 2002 Ryan Hoegg was looking at integrating the commons 
HttpClient to isolate the HTTP level. Did this ever get anywhere?

For various political reasons, using an unstable branch (i.e. 1.2) isn't 
a solution for me at the moment.

Thanks,

Phil

[1] http://sforce.com/us/resources/api.jsp

Re: Modifying HTTP request headers

Posted by Phil Wilson <ph...@philwilson.org>.
Thanks Ryan,

I was planning to use their SOAP API in the long term (for which they do 
provide a sample java client using Apache Axis), but had hoped to use 
XML-RPC for prototyping purposes (for which they don't).

FWIW, I believe that the latest version (2.5) of the Salesforce web 
services only supports SOAP. It would be interesting to know why they 
deprecated XML-RPC support, and I wonder if it had anything to do with 
this issue (as I suspect take-up would have been low).

Thanks for the pointers to the 2.0 version of the XML-RPC library.

Phil

Ryan Hoegg wrote:

> Hi Phil,
> 
> I used an older version of their web services and 1.1 as released is not 
> a viable option.  I have used Apache XML-RPC to access salesforce.com's 
> API but I basically used 2.0 which is still pre-alpha.  If you want to 
> look into it check out cvs HEAD and look for the CommonsXmlRpcClient.  I 
> posted an example usage to this list a month or two ago.  Unfortunately, 
> that's the real unstable branch.
> 
> IIRC they have an SDK with a java client for their API, and they also 
> offer a SOAP wrapper for their service.  You might try those options.
> 
> -- 
> Ryan Hoegg
> ISIS Networks
> http://www.isisnetworks.net
> 
> Phil Wilson wrote:
> 
>> Hi all,
>>
>> A project I'm working on uses the salesforce.com web services[1]. In 
>> order to use their XML-RPC interface I need to be able to specify the 
>> content of the "Cookie" HTTP request header (the value of which is 
>> specified by the return from an initial login).
>>
>> Is there any way of doing this in the 1.1 release? I know that towards 
>> the end of 2002 Ryan Hoegg was looking at integrating the commons 
>> HttpClient to isolate the HTTP level. Did this ever get anywhere?
>>
>> For various political reasons, using an unstable branch (i.e. 1.2) 
>> isn't a solution for me at the moment.
>>
>> Thanks,
>>
>> Phil
>>
>> [1] http://sforce.com/us/resources/api.jsp
> 
> 
> 
> 
> .
> 

Re: Modifying HTTP request headers

Posted by Ryan Hoegg <rh...@isisnetworks.net>.
Hi Phil,

I used an older version of their web services and 1.1 as released is not 
a viable option.  I have used Apache XML-RPC to access salesforce.com's 
API but I basically used 2.0 which is still pre-alpha.  If you want to 
look into it check out cvs HEAD and look for the CommonsXmlRpcClient.  I 
posted an example usage to this list a month or two ago.  Unfortunately, 
that's the real unstable branch.

IIRC they have an SDK with a java client for their API, and they also 
offer a SOAP wrapper for their service.  You might try those options.

--
Ryan Hoegg
ISIS Networks
http://www.isisnetworks.net

Phil Wilson wrote:

> Hi all,
>
> A project I'm working on uses the salesforce.com web services[1]. In 
> order to use their XML-RPC interface I need to be able to specify the 
> content of the "Cookie" HTTP request header (the value of which is 
> specified by the return from an initial login).
>
> Is there any way of doing this in the 1.1 release? I know that towards 
> the end of 2002 Ryan Hoegg was looking at integrating the commons 
> HttpClient to isolate the HTTP level. Did this ever get anywhere?
>
> For various political reasons, using an unstable branch (i.e. 1.2) 
> isn't a solution for me at the moment.
>
> Thanks,
>
> Phil
>
> [1] http://sforce.com/us/resources/api.jsp