This is working as expected in majority of client machines, only few machine have this problem identified. We are sending the URL to WebDEV Server request as encoded, so it should be received in WebDEV handler as encoded string and we will decode it there. ![]() This issue is occurring in few machines only, majority of machines, its working fine.Īny idea, Why some version of Microsoft Office is automatically decode the URL before sending to server? Due to this, server code will again decode the requested URL and it will cause a double decode issue. WebDAV URL: User name and password: your IONOS HiDrive login email address and password Important: Activate WebDAV in Ionos HiDrive: Settings Access rights and protocols. We have verified it in Fiddler, URL is decoded by client machine itself before sending to the server. WebDAV setup You can access your HiDrive files using the DAVx WebDAV mounts feature. This request is successfully reaching in the C# WebDAV handler, but the URL path is automatically decoded by ms-word before sending to the server which is not expected(After decoded - /Test/SampleTestDocument.docx). Redirect URL, Modify Headers & Mock APIs. Redirect URL, Modify Headers, Mock APIs, Modify Response, Insert Scripts. The new user will receive an email with an invitation to HiDrive and, after confirming, will be able to. Enter the data of the new user and assign access rights as well as protocols that can be used by the user. ![]() Connect to a network drive, WebDAV client. In the HiDrive menu on the left, click Administration > Users. We explicitly encoded the URL before invoking document URL via ms-word. Create a temporary WebDAV folder for you that can sync with your Google Drive files. Ms-word:ofe%7Cu%7Chttp%3A%2F%2FMyWebDavServer%2Fwebdavproxy%2FTest%2FSampleTestDocument.docx We are using below URL to open the document in Word via WebDAV server. We implemented our own WebDAV server as C# HTTP handler running on IIS.
0 Comments
Leave a Reply. |