On Thu, 2011-03-10 at 15:02 +0530, manasa k wrote: > As mentioned, I have attached 2 log files. > * logs_withoutProxy.txt - Here connection is establised directly > and gives the required result. > * logstosend_withProxy.txt - Here connection is established via > proxy, which returns 400 Bad request.
I suspect the 400 response was generated by the target server. The proxy merely forwarded it to the client. > From what we analysed, while sending the Authorization header in the > final step URI attribute has value > http://renderv3.mappoint.net/render-30/RenderService.asmx (when > requesting via proxy). But otherwise only the relative > URI /render-30/RenderService.asmx is sent. Sending relative URI seems > to be the common practice when checked in Browser and also in specs. > Requesting your prompt reply. > > The uri attribute is expected to contain a copy of the original request-URI which is absolute in case of proxied requests. I see nothing wrong with the request generated by HttpClient. If you have access to the proxy server, try capturing messages transmitted between the proxy and the target server. If you are a paying Microsoft customer, try approaching their customer support for assistance. Oleg --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
