As mentioned in the October release notes,
(如十月发行说明中所述，)
DocuSign will be making a change to the URL returned by the following API endpoint:
(DocuSign将对以下API端点返回的URL进行更改：)
https://developers.docusign.com/esign-rest-api/reference/Envelopes/EnvelopeViews/createRecipient
(https://developers.docusign.com/esign-rest-api/reference/Envelopes/EnvelopeViews/createRecipient)
The URL returned by this endpoint will be significantly longer.
(该端点返回的URL将明显更长。)
This is currently limited by IE11 which has a URL length limit of 2083 characters but DocuSign reserves the right to increase the URL length beyond this limitation in the future.(当前受IE11限制，IE11的URL长度限制为2083个字符，但DocuSign保留将来将URL长度增加到此限制之外的权利。)
We are using above API in our application for embedded signing, where application is redirecting a recipient to the URL which are returned by this API.
(我们在应用程序中使用上述API进行嵌入式签名，其中应用程序将收件人重定向到此API返回的URL。)
Now main question is that what happen if user is using IE 11 and URL returned by this API is exceeded IE 11 URL limit, Will this change work for IE 11 user as it is?
(现在的主要问题是，如果用户使用的是IE 11，并且此API返回的URL超出了IE 11 URL限制，会发生什么情况？此更改是否对IE 11用户有效？)
If no then how IE 11 user can use embedded signing functionality?(如果不是，那么IE 11用户如何使用嵌入式签名功能？)
// JavaScript code to redirect user
window.location.href = recipientViewUrl; (URL return by above API)
