Empty HTTP request received in SAP RFC test connection type G

[Former Member]

Hi all,

While checking the RFC connection i am getting error,

response_line HTTP/1.0 500 Empty HTTP request received

server_protocol HTTP/1.0

status_code 500

status_reason Empty HTTP request received

Please let me know if this is right.

[abhay_rajhans2]

Hi Arunsri,

We are facing same issue.

Can you pls guide how you resolved this issue?

[Former Member]

I am getting the same text when executing a RFC destination Test for H type. The same destination is used in an inbound interface to PI and the Sender party getting 500 HTTP error. Is there are any connection between the error i get during my RFC test and the error which the thirp party sender getting. There is no message in PI to anaylyse.. not in moni..not in RWB!

[MichalKrawczyk]

Hi,

>>>Please let me know if this is right.

right for what ?

with RFC (for PI) we use RFC dest type 3

for PI - http dest we use dest type - H

we don't use type G for PI configuration (unless you do something specific)

Regards,

Michal Krawczyk

[Former Member]

Hi,

We are trying to connect to an external server. So, we are using Connection Type as G.

RFC connection Test status is 500.

But in our case, Idoc is getting generated but it is in the XI Box, throwing the below error,

<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>

- <!-- Call Adapter

-->

- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">

<SAP:Category>XIServer</SAP:Category>

<SAP:Code area="SECURITY">SECURITY_VERIFY_ERROR</SAP:Code>

<SAP:P1>Check Signature</SAP:P1>

<SAP:P2 />

<SAP:P3 />

<SAP:P4 />

<SAP:AdditionalText>Signature error Error while valdiating the digital signature. Theerror was com.sap.security.core.ws.wss.NoSecurityHeaderException No wsse:Security header has been defined for role soap:finalActor. Please verify the</SAP:AdditionalText>

<SAP:ApplicationFaultMessage namespace="" />

<SAP:Stack>Error during message security handling in inbound channel: Security profile 'Check Signature'</SAP:Stack>

<SAP:Retry>M</SAP:Retry>

</SAP:Error>

Since the RFC is working now, we were not able to find what is the issue. Even SSL certificates are valid.

[former_member181985]

That is perfectly valid.

Where you are using this RFC connection.