Results 1 to 3 of 3

Thread: [SOLVED] soap request header elements to force response header to contain notify/refr

  1. #1
    Join Date
    Oct 2005
    Location
    Emeryville, CA US
    Posts
    22
    Rep Power
    10

    Default [SOLVED] soap request header elements to force response header to contain notify/refr

    Is there a specific set of tags in the headers of a SOAP request to the user service that will force the response to contain the refresh/notify elements?

    We use the SOAP API to integrate one of our sites with Zimbra. One integration is to show users the number of unread e-mails in their INBOX on our site. We had been sending a NoOpRequest, without any special header content, to try to get the refresh/notify content and that appeared to be working fairly well until recently. We installed Zimbra Proxy and now we don't appear to be getting back the refresh/notify a lot of the time anymore.

  2. #2
    Join Date
    Sep 2006
    Posts
    252
    Rep Power
    9

    Default

    Yes, i found this last night too.

    Now you need to send the session id in order to receive a notify object back from the server if there are changes.

  3. #3
    Join Date
    Oct 2005
    Location
    Emeryville, CA US
    Posts
    22
    Rep Power
    10

    Default

    Ah, interesting. We were generally sending the session id, -except- in the cases when we wanted to try to force a response to contain the notify headers.

    Anyway, I wound up not relying on the headers and going with a different approach that requires a little more I/O overhead. We're sending a GetFolderRequest and parsing that to get the number of unread e-mails.

Similar Threads

  1. Replies: 6
    Last Post: 03-17-2006, 10:40 AM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •