OK, I'll create a reproducible case using anonymized data so it might
take a day or so.


Eric

-----Original Message-----
From: Manjula Peiris [mailto:manj...@wso2.com] 
Sent: Tuesday, May 05, 2009 1:24 AM
To: Apache AXIS C User List
Subject: Re: Missing data when going through proxy server
Importance: Low


Create a JIRA and attach the two responses(with HTTP headers) and send
the issue url to this thread. We can have a look.

Thanks,
-Manjula.

On Mon, 2009-05-04 at 12:53 -0400, Eric Hsiung wrote:
> Hello, everybody.
> 
> I have a problem that I've been grappling with for days without any 
> significant progress, hoping someone can help.
> 
> I have a client using the stub code generated by Axis2/C 1.5. It is 
> talking to a Java web services server that has stub code generated by 
> Axis2 1.4.1.
> 
> Some the the web service requests generate large responses, maybe a 
> string with 130K characters. When the client talks directly to the 
> server, then everything works fine. But when the client talks to the 
> server through a proxy server then the response comes back incomplete.

> The Axis2/C stub returns a response but some of the fields are null 
> (like the big string field).
> 
> I found this https://issues.apache.org/jira/browse/AXIS2C-936 and I 
> can deal with it by checking for NULLs in the response, but the 
> question is why is the response incomplete?
> 
> I've tried this with Squid and Privoxy as the proxy servers and both 
> exhibit the same behavior. I've used tools like SoapUI and Paros to 
> see the response coming back through the proxy server and they are 
> fine (the big text string is present). So why doesn't my client app 
> see it? I don't think it is length related since I've tested with 
> shorter response strings (a few hundred characters) and the problem 
> still happens.
> 
> I also implemented a test program using gSOAP and it worked fine 
> through the proxy server.
> 
> Has anybody seen this problem with proxy servers before? Any 
> suggestions as to what might be wrong? Thanks for any assistance.
> 
> 
> Eric
> 
> 
> 
> 
> 

Reply via email to