Hey Jochem,

Sorry for the delay -- some times we get back logged with customers we have contracts with and our free support doesn't get the attention it deserves.

Please verify that your user account has permission to view this message. Does this happen for all messages?

Thanks,

Brad

Jochem,

Looks like I didn't have as much time today as I thought; however, I'm still cognizant of this. I will work on it tonight.

- Brad

Jochem,

I was never able to reproduce this. Attached is a .NET client I used to connect to the server via SOAP and download the image (the attachment for the message you listed earlier). Please review it and see if there is anything I'm doing that you're not...it looks like the key for my client was just sending the correct cookies?

- Brad

Jochem,

Sorry, I've always found C# to be very verbose -- any experience with OO languages makes it rather easy to read. None the less, here are the HTTP headers and their payloads.

    POST /rpc/soap/ForumService HTTP/1.1\r\n
    Content-Type: text/xml; charset=utf-8\r\n
    [truncated] Cookie: jive.recentHistory=312c3435373730393b;jive.user.loggedIn=true;AUID=atK8ce62e9p8yR%2BBmIRdxVhZn3w41YecIgpWVFUdxqOyhAs%2FlgIAAy6UuHKa0h5VxN%2FHQKHwAZO3%0AQ2lvoywUaQ%3D%3D;s_vi=[CS]v1|253A731085012678-4000010D400067F8[CE];
    VsDebuggerCausalityData: uIDPo1bnV9JK4XxBro7uCYwvCqQAAAAARRQFA+GUfU6MawQh8oFAiRghaL/R8s1Cn/7Rx8eyeu4ACQAA\r\n
    SOAPAction: ""\r\n
    Host: forums.adobe.com\r\n
    Content-Length: 342\r\n
    Expect: 100-continue\r\n
    Connection: Keep-Alive\r\n
    \r\n
    <s:Envelope>
        xmlns:s="http://schemas.xmlsoap.org/soap/envelope/"
        <s:Body>
            xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
            xmlns:xsd="http://www.w3.org/2001/XMLSchema"
            <getAttachmentsByMessageID>
                xmlns="http://jivesoftware.com/clearspace/webservices"
                <messageID>
                    xmlns=""
                    2085697
                    </messageID>
                </getAttachmentsByMessageID>
            </s:Body>
        </s:Envelope>

    HTTP/1.1 200 OK\r\n
    Date: Fri, 28 Aug 2009 08:45:02 GMT\r\n
    SOAPAction: ""\r\n
    Content-Type: text/xml;charset=UTF-8\r\n
    Vary: Accept-Encoding,User-Agent\r\n
    JP: D=86853 t=1251449102079095\r\n
    Keep-Alive: timeout=5, max=100\r\n
    Connection: Keep-Alive\r\n
    Transfer-Encoding: chunked\r\n
    Set-Cookie: BIGipServerPool_53_ENT2=756582666.22555.0000; path=/\r\n
    \r\n
    <soap:Envelope>
        xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"
        <soap:Body>
            <ns1:getAttachmentsByMessageIDResponse>
                xmlns:ns1="http://jivesoftware.com/clearspace/webservices"
                <return>
                    <ID>
                        12926
                        </ID>
                    <objectType>
                        13
                        </objectType>
                    <contentType>
                        image/jpeg
                        </contentType>
                    <data>
                        [truncated] <!-- buncha base64 stuff -->
                        </data>
                    <name>
                        imagerunready.jpg
                        </name>
                    </return>
                </ns1:getAttachmentsByMessageIDResponse>
            </soap:Body>
        </soap:Envelope>

In the request headers there are a few fields thrown in there by Visual Studio/the WCF stack but they look mostly innocuous in this context. The reason I throught it was the cookies was that I kept getting varied results and adding more cookies until it finally worked. The cookies that I am sending in the request are

1. jive.server.info
2. JSESSIONID
3. AUID
4. s_vi
5. jive.user.loggedIn
6. WCDServer
7. jive.recentHistory

Hope that helps some...

Good to hear. I hope you are finding the REST API a bit more reliable. Also, you might be interested to know that I think that Adobe will be upgrading to a newer version of Clearspace in the near future. This should provide some additional stability on your end.