Document Editor not working since 2.0
Submitted by Ben_Charlton on Wed, 06/11/2019 - 12:13
So the Document editor no longer works in 2.1 for us
Our setup is tomcat running on http forwarded via apache running https
Basically we dont use tomcat's inbuilt HTTPS handler because its certificat handling is terrible and difficult to use automated certificate renewal.
The error I suspect occurs because
1. We forward all http request to https - but I am betting the java app cant do it.
so there are 2 issues
1.
<?xml version="1.0" encoding="utf-8"?> <!-- ~ Version: 1.0 ~ ~ The contents of this file are subject to the OpenVPMS License Version ~ 1.0 (the 'License'); you may not use this file except in compliance with ~ the License. You may obtain a copy of the License at ~ http://www.openvpms.org/license/ ~ ~ Software distributed under the License is distributed on an 'AS IS' basis, ~ WITHOUT WARRANTY OF ANY KIND, either express or implied. See the License ~ for the specific language governing rights and limitations under the ~ License. ~ ~ Copyright 2017 (C) OpenVPMS Ltd. All Rights Reserved. --> <jnlp spec="1.6+" codebase="http://surgery.kalingaparkvetsurgery.com.au/openvpms/webstart"> <information> <title>OpenVPMS Editor Launcher</title> <vendor>OpenVPMS Pty Ltd</vendor> <homepage href="http://openvpms.org"/> <description>Launches editors for documents in OpenVPMS</description> <offline-allowed/> </information> <security> <all-permissions/> </security> <resources> <java version="1.6+"/> <property name="jnlp.packEnabled" value="true"/> <jar href="openvpms-webdav-launcher-1.9.2.jar" main="true"/> </resources> <application-desc main-class="org.openvpms.web.webdav.launch.EditorLauncher"> <argument>http://surgery.kalingaparkvetsurgery.com.au/openvpms/document/f727f980-12ef-4a27-b786-b5ede30a3c0c/300697/Export%20Dog%20-%20NZ%20-%20Cert%20A%20-%20Initial%20-%20Hope%20Shaun%20-%206%20Nov%202019.odt</argument> </application-desc> </jnlp>
the arguement is http ..
2.
com.sun.deploy.net.FailedDownloadException: Unable to load resource: http://surgery.kalingaparkvetsurgery.com.au/openvpms/webstart/openvpms-w... at com.sun.deploy.net.DownloadEngine.actionDownload(Unknown Source) at com.sun.deploy.net.DownloadEngine.downloadResource(Unknown Source) at com.sun.deploy.cache.ResourceProviderImpl.getResource(Unknown Source) at com.sun.deploy.cache.ResourceProviderImpl.getResource(Unknown Source) at com.sun.javaws.LaunchDownload$DownloadTask.call(Unknown Source) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source)
java.lang.SecurityException: illegal URL redirect at com.sun.deploy.net.HttpUtils.followRedirects(Unknown Source) at com.sun.deploy.net.BasicHttpRequest.doRequest(Unknown Source) at com.sun.deploy.net.BasicHttpRequest.doGetRequestEX(Unknown Source) at com.sun.deploy.net.DownloadEngine.actionDownload(Unknown Source) at com.sun.deploy.net.DownloadEngine.downloadResource(Unknown Source) at com.sun.deploy.cache.ResourceProviderImpl.getResource(Unknown Source) at com.sun.deploy.cache.ResourceProviderImpl.getResource(Unknown Source) at com.sun.javaws.LaunchDownload$DownloadTask.call(Unknown Source) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source)
#### Unable to load resource: http://surgery.kalingaparkvetsurgery.com.au/openvpms/webstart/openvpms-webdav-launcher-1.9.2.ja
I think that clarifies it
Re: Document Loader not working since 2.0
Incidently the same error occurs if you access the app via
http://surgery.kalingaparkvetsurgery.com.au:8080/openvpms/app/1
which is bypassing all apache proxying.
Re: Document Editor not working since 2.0
This is unsupported. There would need to be a facility to override the URLs produced by the WebDAV service.
Re: Document Editor not working since 2.0
This is fixed by updating the server.xml file of tomcat to properly handle proxying.