function readOnly(count){ }
Starting November 20, the site will be set to read-only. On December 4, 2023,
forum discussions will move to the Trailblazer Community.
+ Start a Discussion

http.send() to other Salesforce orgs returns with "Read timed out" exception

I've created a publicly accessible REST service that has been working for a couple weeks.  I can GET its URI using Firefox, and POST its URI using curl -- both without authentication (as designed).


What has stopped working today is the ability to POST to it from another SF org using Salesforce.  The simple code below is timing-out.


Http http = new Http();
HttpRequest request = new HttpRequest();
Httpresponse response = http.send(request);


To verify the destination is working, I've tested the following curl command and it works, and returns in less than a second.


time curl -v -d ignore=true
> POST /services/apexrest/FeedbackRest HTTP/1.1
> User-Agent: curl/7.21.6 (i686-pc-linux-gnu) libcurl/7.21.6 OpenSSL/1.0.0e zlib/ libidn/1.22 librtmp/2.3
> Host:
> Accept: */*
> Content-Length: 11
> Content-Type: application/x-www-form-urlencoded
< HTTP/1.1 200 OK
< Server: 
< Content-Type: application/xml; charset=ISO-8859-1
< Date: Sat, 24 Nov 2012 18:53:36 GMT
< Transfer-Encoding: chunked
* Connection #0 to host left intact
* Closing connection #0
* SSLv3, TLS alert, Client hello (1):
<?xml version="1.0"?><feedback version="1.0" type="Success" id="a0b60000005T4lMAAS"></feedback>
real	0m0.827s
user	0m0.008s
sys	0m0.020s

This had been working earlier in the week, but is suddenly not working today.  The remote sites are setup correctly else I would have gotten an invalid site error.  I have't exceeded a governor limit else I would have gotten a limit exception.


Is anyone else noticing this issue?


I'm beginning to think the problem is on the receiving end.  I'm able to send/recieve find between na11 and na12.  Perhaps it's just a problem with na4, or something else is going on.