> For the complete documentation index, see [llms.txt](https://docs.apryse.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.apryse.com/web/changelogs/webviewer-server/server-changelog-2020.md). # WebViewer Server 2020 Changelog World's #1 PDF SDK Library for Web, Mobile, Server, Desktop ### 1.5.4 - November 6th * Apryse Core Library updated with more general document fixes * Updated Apache Tomcat to 9.0.39 * Improved overall CORS handling * Security: Fixed issue that could expose local files during HTML conversion * Security: Fixed CloudFormation template to no longer expose IMDS metadata when improperly configured ### 1.5.3 - September 21st * Apryse Core Library updated to 8.0 * Improved default configuration handling on Windows and Linux * Added support for TRN\_CAD\_XREF\_CONFIG\_URL option * Added server performance details to logging * XLS conversion is now done by Apryse Core, was previously handled by LibreOffice * Removed Tomcat version from error HTTP error messages ### 1.5.2 - August 4th * Fixed many document failures with many office document formats, focused on PPT * The Docker container now runs only as a user, this prevents permission problems and removes the need for the previous TRN\_AZURE\_WEBAPP\_COMPAT - this option has been removed * Updated both OpenJDK 1.8 and Apache Tomcat to 1.8.262 and 9.0.37 respectively to address security issues * Added log rotation for internal server logs, this will prevent log build up from filling disk space * Added default HEALTHCHECK in both HAProxy and the WebViewer Server containers, this is checked by Docker to mark whether the containers are healthy or not * Fixed various font selection errors across many documents ### 1.5.1 - April 28th * Apryse Core Library updated to 7.1.3 * Improves office format rendering and server stability * Fixed crash caused by multiple simultaneous LibreOffice conversions * Fixed crashes caused by documents on annotation merge with annotations lacking page numbers or default appearances. * Fixed error on restart which could cause files requiring software rasterization to fail * Increased allowed zoom levels for returned image tiles on PDF render * Added files which were being ignored by cache management to prevent image from consuming excess disk * Added new logging data on health failures and job execution * Improved EML and MSG rendering * Added annotation merging through option `xfdf` to GetPDF * Corrected issue with GetThumb not working with query parameters * Fixed remaining temporary file issues caused by shared volume mounts * [TRN\_FETCH\_TIMEOUT\_MS](/web/webviewer-server/wv-server-config.md#fetch-timeout) option added, server file fetches will default to a 20 second timeout when waiting for first read/connection establishment * Renamed `TRN_DEBUG_DISABLE_CLIENT_BACKEND_SWITCH` to `TRN_DISABLE_CLIENT_SIDE_RENDERING` ### 1.5.0 - March 2nd * [Apryse Core updated to version 7.1](/core/changelogs/version-7/7-1-0.md) * Tomcat version updated from `9.0.6` to `9.0.30` * [TRN\_HUMAN\_READABLE\_TIMESTAMPS](/web/webviewer-server/wv-server-config.md#readable-timestamps-on-windows-webViewer-server) option added * [TRN\_ALLOW\_ORIGINS](/web/webviewer-server/wv-server-config.md#restrict-client-origins) option added * [TRN\_FORCE\_URL\_RECHECK](/web/webviewer-server/wv-server-config.md#force-url-rechecking) option added * Added support for the file formats `vsd`, `vsdx`, `eml`, `msg`, `xhtml` and `dwf` * Added support for the `rvt` format (Windows server hosts only) * Upgraded server demo to WebViewer 6, was previously using WebViewer 5.2 * [Added 'linearize' option to GetPDF](/web/webviewer-server/wv-server-usage.md#linearize) * Improved performance under load * Improved memory handling * Improved server logging * Improved error checking and reporting * [\[wv-loadbalancer\] Added stickiness by query parameter](/web/webviewer-server/wv-server-hardware-and-network.md#stickiness-using-query-parameters) * \[wv-loadbalancer] Added configuration change to load balancer to prevent rare redirections to incorrect servers * [Added silent install option to Windows installer](/web/webviewer-server/deployment/wv-server-deploying-without-docker.md#performing-a-silent-install) * Annotation appearances no longer show up different than their original state if downloaded from WebViewer Server through WebViewer's download or print functions * Fixed error that could cause cookies forwarded with the `TRN_FORWARD_CLIENT_COOKIES` option to be overwritten by incorrect cookies * Fixes to allow mounting of the 'static\_data' directory across disk volumes * Prevented missing directories from causing WebViewer Server to crash on startup * Unicode characters in file names now work when requesting a XOD link * When authentication options are enabled, WebViewer Server now correctly maintains cookie state when multiple tabs are open. Previously, the opening of successive viewer tabs would change the authentication cookie on prior clients breaking their interaction with the server * Removed container names in compose file, this prevents issues when running the setup multiple times * Windows installer now correctly sets up the WebViewer service on all machines * Fixed issue with url encoding with some types of file links --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.apryse.com/web/changelogs/webviewer-server/server-changelog-2020.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.