This content has been machine translated dynamically.
Dieser Inhalt ist eine maschinelle Übersetzung, die dynamisch erstellt wurde. (Haftungsausschluss)
Cet article a été traduit automatiquement de manière dynamique. (Clause de non responsabilité)
Este artículo lo ha traducido una máquina de forma dinámica. (Aviso legal)
此内容已经过机器动态翻译。 放弃
このコンテンツは動的に機械翻訳されています。免責事項
이 콘텐츠는 동적으로 기계 번역되었습니다. 책임 부인
Este texto foi traduzido automaticamente. (Aviso legal)
Questo contenuto è stato tradotto dinamicamente con traduzione automatica.(Esclusione di responsabilità))
This article has been machine translated.
Dieser Artikel wurde maschinell übersetzt. (Haftungsausschluss)
Ce article a été traduit automatiquement. (Clause de non responsabilité)
Este artículo ha sido traducido automáticamente. (Aviso legal)
この記事は機械翻訳されています.免責事項
이 기사는 기계 번역되었습니다.책임 부인
Este artigo foi traduzido automaticamente.(Aviso legal)
这篇文章已经过机器翻译.放弃
Questo articolo è stato tradotto automaticamente.(Esclusione di responsabilità))
Translation failed!
RPC over HTTPS
Is it mandatory to create a service class to accelerate RPC over HTTPS connections?
Creating a new service class is an optional task. You can use an existing HTTPS service class. However, to create reports specifically for RPC over HTTPS connections, you must create a new service class and bind the SSL profile to it. If you do not want to create a service class for RPC over HTTPS connections, you can bind the SSL profile you have created to the Web (Private-Secure) service class.
I have not created any service class for the RPC over HTTPS applications. How will this affect the reporting of the RPC over HTTPS connections?
When you upgrade the appliance to release 7.3, the RPC over HTTPS applications that are created do not belong to any service class. As a result, all RPC over HTTPS connections are listed as the TCP Other connections in the reports. If you want to classify these connections as RPC over HTTPS connections, you must create a service class for these applications.
Is there a default service class for RPC over HTTPS on the appliance?
No. The appliance has only default applications, and not default service classes. You must create the service class for an application.
Does the appliance provide any SSL compression benefits to the RPC over HTTPS connections?
No. The appliance does not provide any SSL compression benefits to the RPC over HTTP connections. Compression benefits are available only for encryption and decryption of HTTPS traffic.
Similar to MAPI, does the appliance optimize latency for RPC over HTTPS connections?
No. The appliance does not optimize latency for RPC over HTTPS.
Is MAPI over HTTP different from RPC over HTTPS?
Yes. MAPI over HTTP is a new protocol supported on Microsoft Exchange Server 2013 SP1 or later.
What is the difference between RPC over HTTPS settings on client-side and server-side Citrix SD-WAN WANOP appliances?
Except for creating a service class and adding RPC over HTTPS applications to it, you do not need any additional configuration on a client-side Citrix SD-WAN WANOP appliance.
What happens if I configure the SSL profile in transparent proxy mode?
Some Exchange servers require TLS session ticket support. To accelerate connections to these servers, you need to create an SSL profile with split proxy, because transparent proxy mode does not support TLS session tickets.
If a load balancing setup is used for the Microsoft Exchange Server, which destination IP address should I add to the filter rule when creating an RPC over HTTPS service class?
If you are using a load balancing appliance, add its virtual IP (VIP) address to the filter rule when creating an RPC over HTTP service class.
How can I differentiate between the MAP and RPC over HTTPS traffic in the Outlook (MAPI) page?
You can differentiate the traffic based on applications shown on the Outlook (MAPI) page. For example, MAPI and RPC over HTTPS are used for the following applications:
-
MAPI: MAPI and eMAPI
-
RPC over HTTPS: HTTP MAPI, HTTP eMAPI, HTTPS MAPI, and HTTPS eMAPI
Share
Share
In this article
- Is it mandatory to create a service class to accelerate RPC over HTTPS connections?
- I have not created any service class for the RPC over HTTPS applications. How will this affect the reporting of the RPC over HTTPS connections?
- Is there a default service class for RPC over HTTPS on the appliance?
- Does the appliance provide any SSL compression benefits to the RPC over HTTPS connections?
- Similar to MAPI, does the appliance optimize latency for RPC over HTTPS connections?
- Is MAPI over HTTP different from RPC over HTTPS?
- What is the difference between RPC over HTTPS settings on client-side and server-side Citrix SD-WAN WANOP appliances?
- What happens if I configure the SSL profile in transparent proxy mode?
- If a load balancing setup is used for the Microsoft Exchange Server, which destination IP address should I add to the filter rule when creating an RPC over HTTPS service class?
- How can I differentiate between the MAP and RPC over HTTPS traffic in the Outlook (MAPI) page?
This Preview product documentation is Cloud Software Group Confidential.
You agree to hold this documentation confidential pursuant to the terms of your Cloud Software Group Beta/Tech Preview Agreement.
The development, release and timing of any features or functionality described in the Preview documentation remains at our sole discretion and are subject to change without notice or consultation.
The documentation is for informational purposes only and is not a commitment, promise or legal obligation to deliver any material, code or functionality and should not be relied upon in making Cloud Software Group product purchase decisions.
If you do not agree, select I DO NOT AGREE to exit.