<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: ABAP Proxy throws HTTP-400 error in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/abap-proxy-throws-http-400-error/m-p/5352326#M1232371</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Wesley,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I would be obliged if you can tell me exactly where you put style=document.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Prosenjit.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 05 May 2009 09:54:41 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2009-05-05T09:54:41Z</dc:date>
    <item>
      <title>ABAP Proxy throws HTTP-400 error</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/abap-proxy-throws-http-400-error/m-p/5352323#M1232368</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I've created an ABAP Proxy/Enterprise Service in ECC6.0 to consume a webservice that is created in NetWeaver 2004s. Now, when I want to test the proxy, it gives me the error message: &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;SOAP:1.007 SRT: Unsupported xstream found: ("HTTP Code 400  : Bad Request")&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The error originates from class &lt;STRONG&gt;CX_AI_SYSTEM_FAULT&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I don't know if it is related to the proxy or with some system settings on ECC 6.0/Netweaver2004s.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Any help or document reference is appreciated.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 12 Mar 2009 16:17:04 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/abap-proxy-throws-http-400-error/m-p/5352323#M1232368</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2009-03-12T16:17:04Z</dc:date>
    </item>
    <item>
      <title>Re: ABAP Proxy throws HTTP-400 error</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/abap-proxy-throws-http-400-error/m-p/5352324#M1232369</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I investigated a little and here are a couple of things you could try:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;- In note 1139406, they are talking about a scenario with HTTP error 404... I realize it is different than the 400 you get, but it may be worth checking if you have a similar problem as described there - it may give a clue what your problem is.&lt;/P&gt;&lt;P&gt;- Try to check if the endpoint URL to which the request is sent is correct... it may be missing the style parameter, like ?style=document. Go to SOAMANAGER and take a look at the system settings, perhaps there is a wrongly formulated URL that is missing the style parameter.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope this helps a little...&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 12 Mar 2009 18:31:53 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/abap-proxy-throws-http-400-error/m-p/5352324#M1232369</guid>
      <dc:creator>Tamas_Hoznek</dc:creator>
      <dc:date>2009-03-12T18:31:53Z</dc:date>
    </item>
    <item>
      <title>Re: ABAP Proxy throws HTTP-400 error</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/abap-proxy-throws-http-400-error/m-p/5352325#M1232370</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Indeed, adding the comment ?style=document next to the logical port WSDL did the work!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thx&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 17 Mar 2009 12:45:13 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/abap-proxy-throws-http-400-error/m-p/5352325#M1232370</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2009-03-17T12:45:13Z</dc:date>
    </item>
    <item>
      <title>Re: ABAP Proxy throws HTTP-400 error</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/abap-proxy-throws-http-400-error/m-p/5352326#M1232371</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Wesley,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I would be obliged if you can tell me exactly where you put style=document.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Prosenjit.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 05 May 2009 09:54:41 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/abap-proxy-throws-http-400-error/m-p/5352326#M1232371</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2009-05-05T09:54:41Z</dc:date>
    </item>
    <item>
      <title>Re: ABAP Proxy throws HTTP-400 error</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/abap-proxy-throws-http-400-error/m-p/5352327#M1232372</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Prosenjit,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you run transaction &lt;EM&gt;SOAMANAGER&lt;/EM&gt; on R/3, you can configure your proxy consumer by defining a logical port pointing to the webservice. In the URL Access Path, extend your input with &lt;STRONG&gt;?style=document&lt;/STRONG&gt;. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Here's an image of that particular screen:&lt;/P&gt;&lt;P&gt;[SOAMANAGER - Transport Settings|http://users.telenet.be/computerschaak/SAPWebServices/Config.jpg]&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Cheers,&lt;/P&gt;&lt;P&gt;Wesley&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 12 May 2009 13:07:54 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/abap-proxy-throws-http-400-error/m-p/5352327#M1232372</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2009-05-12T13:07:54Z</dc:date>
    </item>
  </channel>
</rss>

