cancel
Showing results for 
Search instead for 
Did you mean: 

/alfresco/service/api/node fails from Internet Explorer

chatch
Champ in-the-making
Champ in-the-making
Content returned via the get content by node service fails when called from Internet Explorer but is fine from Firefox.

Eg. the following in our system failed /alfresco/service/api/node/content/workspace/SpacesStore/413ab51a-36b1-11dc-8f1f-e99e15fc0438

however using the link /alfresco/d/d/workspace/SpacesStore/3ee469a4-36b1-11dc-8f1f-e99e15fc0438/p1_en.rtf was fine.

Has anyone seen this?
3 REPLIES 3

davidc
Star Contributor
Star Contributor
Fails in what way?

Have you tried adding /p1_en.rtf to the first URL?

damonrand
Champ in-the-making
Champ in-the-making
On further inspection we are only getting this problem with binary (eg. RTF) documents at the moment (html and xml work fine).

Message in MSIE is "Internet explorer was not able to open this site. The requested site is either unavailable or cannot be found. Please try again later."

Initially we thought it might have been our SSL proxy causing the problem but that problem occurs with a direct connection to the Tomcat box on 8080.

Adding /p1_en.rtf gives the same problem. Perhaps MSIE doesn't like the way some of response headers are set?

Damon.

damonrand
Champ in-the-making
Champ in-the-making
Here are the headers for the link that works.. I think MSIE is having problems with those no-cache headers on binary files.

Date: Sat, 21 Jul 2007 13:20:56 GMT
Server: Apache-Coyote/1.1
Last-Modified: Sat, 21 Jul 2007 12:34:56 GMT
Content-Type: application/pdf;charset=UTF-8
Via: 1.1 intranet.amnesty.org

And for the link that doesn't work

Date: Sat, 21 Jul 2007 13:18:22 GMT
Server: Apache-Coyote/1.1
Cache-Control: no-cache
Pragma: no-cache
Last-Modified: Sat, 21 Jul 2007 12:34:56 GMT
Content-Type: application/pdf;charset=UTF-8
Via: 1.1 intranet.amnesty.org

Damon.