Hi there,

We are having several issues between salesforce and our company proxy / reverseproxy. Here SalesForce is acting as a client, that is calling a WebService that is in our internal servers.

We sniffed all that is comming from Salesforce and realized that the HTTP header received from SalesForce is not that clean.

Below is part of the header :

______________________________________________

POST /xxx/yyy.svc HTTP/1.0\r\n

SFDC_STACK_DEPTH: 1\r\n

User-Agent: SFDC-Callout/24.0\r\n

Accept: text/xml\r\n

Content-Type: text/xml; charset=UTF-8\r\n

...

Via: 1.1 proxy-chi.net.salesforce.com:8080 (squid)\r\n

X-Forwarded-For: 10.232.12.23\r\n

Cache-Control: max-age=259200\r\n

Connection: keep-alive\r\n

______________________________________________

Strangely, SalesForce is using the http 1.0, did they know that the http 1.1 is out for a while, and that it corrected several issues related to the http 1.0, specifically to the handling of the Connection Keep-Alive and so on.

All other calls comming from SOAPUI or JMeters are calls that are by default http 1.1, and the Connection is set to Close.

If Salesforce wants to Keep-Alive the connection it has at least to specify a Connection-Token.

I think this is a complete mess on the SalesForce Side.

Question :

 - Do we have access to the version of http when we call a WebService?

 - Can we set the Connection Property of the Http header to Close?

Best Regards,

BizTalk@Paris

Hi there,

We are having several issues between salesforce and our company proxy / reverseproxy. Here SalesForce is acting as a client, that is calling a WebService that is in our internal servers.

We sniffed all that is comming from Salesforce and realized that the HTTP header received from SalesForce is not that clean.

Below is part of the header :

______________________________________________

POST /xxx/yyy.svc HTTP/1.0\r\n

SFDC_STACK_DEPTH: 1\r\n

User-Agent: SFDC-Callout/24.0\r\n

Accept: text/xml\r\n

Content-Type: text/xml; charset=UTF-8\r\n

...

Via: 1.1 proxy-chi.net.salesforce.com:8080 (squid)\r\n

X-Forwarded-For: 10.232.12.23\r\n

Cache-Control: max-age=259200\r\n

Connection: keep-alive\r\n

______________________________________________

Strangely, SalesForce is using the http 1.0, did they know that the http 1.1 is out for a while, and that it corrected several issues related to the http 1.0, specifically to the handling of the Connection Keep-Alive and so on.

All other calls comming from SOAPUI or JMeters are calls that are by default http 1.1, and the Connection is set to Close.

If Salesforce wants to Keep-Alive the connection it has at least to specify a Connection-Token.

I think this is a complete mess on the SalesForce Side.

Question :

 - Do we have access to the version of http when we call a WebService?

 - Can we set the Connection Property of the Http header to Close?

Best Regards,

BizTalk@Paris

Hi there,

We are having several issues between salesforce and our company proxy / reverseproxy. Here SalesForce is acting as a client, that is calling a WebService that is in our internal servers.

We sniffed all that is comming from Salesforce and realized that the HTTP header received from SalesForce is not that clean.

Below is part of the header :

______________________________________________

POST /xxx/yyy.svc HTTP/1.0\r\n

SFDC_STACK_DEPTH: 1\r\n

User-Agent: SFDC-Callout/24.0\r\n

Accept: text/xml\r\n

Content-Type: text/xml; charset=UTF-8\r\n

...

Via: 1.1 proxy-chi.net.salesforce.com:8080 (squid)\r\n

X-Forwarded-For: 10.232.12.23\r\n

Cache-Control: max-age=259200\r\n

Connection: keep-alive\r\n

______________________________________________

Strangely, SalesForce is using the http 1.0, did they know that the http 1.1 is out for a while, and that it corrected several issues related to the http 1.0, specifically to the handling of the Connection Keep-Alive and so on.

All other calls comming from SOAPUI or JMeters are calls that are by default http 1.1, and the Connection is set to Close.

If Salesforce wants to Keep-Alive the connection it has at least to specify a Connection-Token.

I think this is a complete mess on the SalesForce Side.

Question :

 - Do we have access to the version of http when we call a WebService?

 - Can we set the Connection Property of the Http header to Close?

Best Regards,

BizTalk@Paris