Search results

Page title matches

Page text matches

  • == Migrating via REST == ...port via the [http://en.wikipedia.org/wiki/Representational_State_Transfer REST] interface. Currently, contacts and calendar are only imported with the Ex
    8 KB (1,252 words) - 15:03, 11 July 2015
  • ...evel}}|{{ZCS 8.0}}|{{ZCS 7.0}}|{{ZCS 6.0}}|}}Zimbra exposes its data via a REST API. This document is the reference for that functionality. ...rvices that make resources available via a URL. For example, the following REST command retrieves all inbox items as a simple RSS feed:
    10 KB (1,400 words) - 17:19, 5 August 2014
  • ===ZCS User to Another ZCS Server - With Rest & TGZ=== ====Rest And The FMT= Option====
    42 KB (6,459 words) - 19:24, 20 June 2016
  • * "ldap backup not kept with rest of backup" ===Use Of REST And Other Tools For Specific User Data===
    126 KB (19,115 words) - 13:49, 17 May 2017
  • ....example.com server. In addition to the ZCS web interface, clients such as REST and CalDAV clients, Zimbra Connector for Outlook and Zimbra Mobile Sync dev ...he request is routed to the backend mailbox server of the user in the URL. REST, Ca lDAV, and Zimbra Mobile Sync are supported through this mechanism.
    33 KB (4,923 words) - 22:01, 7 June 2016
  • ===Inter-Domain (Company To Company) Item Access [Sharing?] Via Rest=== From /opt/zimbra/doc/rest.txt :
    55 KB (8,406 words) - 13:35, 21 June 2016
  • === REST URL Generation === Source : Admin Guide Draft, 'REST URL Generation'
    11 KB (1,727 words) - 21:57, 7 June 2016
  • * zimbraPublicServiceHostname(Name to be used in public API such as REST or SOAP proxy) - proxy hostname * zimbraPublicServiceProtocol(Protocol to be used in public API such as REST or SOAP proxy) - proxy protocol (http or https)
    13 KB (1,714 words) - 21:52, 7 June 2016
  • ===REST users=== The REST interface always returns the server's view of the appointment. This means t
    11 KB (1,778 words) - 17:24, 24 March 2015
  • ==REST Information== * Rest Overview
    7 KB (1,016 words) - 16:38, 20 June 2016
  • GET_REST_URL("getRestURL", "gru", "{relative-path}", "do a GET on a REST URL relative to the mailbox", Category.MISC, 1, 1, ...T_URL("postRestURL", "pru", "{relative-path} {file-name}", "do a POST on a REST URL relative to the mailbox", Category.MISC, 2, 2,
    78 KB (9,810 words) - 16:31, 1 April 2015
  • ==== Rest of the steps...<br> ==== The rest of the steps are exactly similar to http://wiki.zimbra.com/wiki/Testing:_Se
    8 KB (1,097 words) - 20:15, 25 March 2015
  • ==== Rest of the steps...<br> ==== The rest of the steps are exactly similar to http://wiki.zimbra.com/wiki/Testing:_Se
    7 KB (1,006 words) - 20:22, 25 March 2015
  • ...Zimbra Admin Client and Zimlets. This is how the proxy routes UI and SOAP/REST requests in a split environment. ...am for each client and uses this mailclient server for all subsequent SOAP/REST requests made by that client.
    14 KB (1,585 words) - 03:09, 9 May 2018
  • ...tions around HTTP[S] allows end-users to use this single hostname for ZWC, REST, CalDAV, Zimbra Connector for Outlook, Zimbra Connector for BES, Zimbra Mob ...ll kind of static UI requests (HTML/CSS/JS etc) and Dynamic requests (SOAP/REST/IMAP/POP) to the appropriate upstream server. Here are some other benefits
    15 KB (2,270 words) - 21:51, 7 June 2016
  • ...it out of the zmdiaglog during the heap dump process without affecting the rest of the dump. You will just need to compress the files manually. ...st have a full zmdiaglog (with valid java memory heap dump) along with the rest of the data it collects.
    37 KB (5,360 words) - 13:41, 21 June 2016
  • ...of opinions. I just make a small partition for swap (1.5-2x RAM) and the rest for the whole system. Others will recommend separate partitions for mailst ...ain.com and it'll find the names through nslookup, and it'll be happy. The rest of the install should proceed without errors, except that toward the end it
    14 KB (2,350 words) - 19:51, 25 March 2015
  • DESC 'Name to be used in public API such as REST or SOAP proxy.' DESC 'Port to be used in public API such as REST or SOAP proxy.'
    259 KB (18,916 words) - 04:04, 4 February 2022
  • =REST File Formats= |+ REST file formats
    7 KB (1,103 words) - 21:44, 16 February 2017
  • DESC 'Name to be used in public API such as REST or SOAP proxy.' DESC 'Port to be used in public API such as REST or SOAP proxy.'
    268 KB (19,616 words) - 04:05, 4 February 2022
View (previous 20 | ) (20 | 50 | 100 | 250 | 500)
Jump to: navigation, search