> 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-2021.md).

# WebViewer Server 2021 Changelog

World's #1 PDF SDK Library for Web, Mobile, Server, Desktop

### 1.5.7 - September 10th

* [Apryse core update to 9.1](https://github.com/iKettles/apryse-gitbook/tree/main/core/guides/release-notes.md)
* Added all advanced imaging formats to WebViewer Server (`dcm, tiff, cut, cur, arw, aai, dcr, psd, gif, heic, heif, cals, dds, crw, jng, flif, mat, mtv, nef, orf, pfm, pix, raf`)
* Added `.pub` (Microsoft Publisher) formats
* Encrypted PDFs are now supported, requires WebViewer 8.1
* Added ability to set document locale in WebViewer Server, refer to [this](/web/webviewer-server/wv-server-config.md#set-the-default-office-locale) documentation
* Added `.msg` (Outlook Email) support on Windows and fixed some existing issues with conversion on Linux
* Added [TRN\_DISABLE\_WATCHDOG\_RESTART](/web/webviewer-server/wv-server-config.md#disable-the-watchdog-auto-restart)
* Added AWS/S3 error reporting, for more info on setup follow the guide [here](/web/get-started/faq/container-information.md#crash-collection-on-aws)
* Added [alive](/web/webviewer-server/wv-server-usage.md#life-check) check to determine if the server is functional
* Added the [GetSupportedFormats API](/web/webviewer-server/wv-server-usage.md#getsupportedformats)
* Fixed issue that could cause random crashes when converting at scale.
* Removed packages and excess tooling to reduce the size and vulnerability space and size of the docker image
* Upgraded to Tomcat 10.0.8
* Upgraded the Cloudformation Template to 2.0.0
  * Now supports more options, Application load balancing, fixes scaling, data cleanup and deletion issues
* Added format control to WebViewer Server to prevent erroneous file format exploits
* Improved font support, now includes all Apryse web fonts
* \[Windows] When using WebViewer Server as a Windows service, catalina.base was left undefined. This could cause minor problems in various systems when using the service
* Changed health check to have a greater threshold for marking as unhealthy
* Fix for leftover temp files when file fetches failed on the server - these would show up as leftover download.tmp files in your static\_data/Fetched directory
* Files with Unicode names + symbols now properly download when requested from WebViewer
* Various fixes for document specific crashes
* Added more aggressive cleanup when both `TRN_ENABLE_AUTH_SESSION` and `TRN_ENABLE_SESSION_CACHING` are enabled
* All Tomcat apps are now packaged as WAR files and JSPs no longer are used
* Fixed WVSWrapperAPI to properly POST when uploading a file with XFDF
* General CAD document improvements
* Added restriction to prevent chrome from executing multiple conversions at once, fixes issue that could cause HTML conversion to fail
* Made it so WebViewer Server no longer reveals its system paths during errors
* Removed double fetch calls in some APIs, this will make them more responsive
* Fixed issue with logrotate not properly rotating/deleting some logs in WebViewer Server
* Corrected issue causing SSL keys to fail when installed directly on the server
* Updated software rasterizer used for CAD document formats
* Fixed issue where changing the `TRN_DATA_STORAGE_DIR` directory could cause the server to fail. Now the static data path is properly adjusted to match this variable
* Fixed issue where singleServerMode would cause WebViewer to fail with server version 1.5.6
* Fixed error handling not properly failing with GetThumb and GetPDF
* Fixed issue where the Windows service would not timeout
* Fixed issue with GetThumb and GetPDF where documents with extensions other than PDF would still be treated as PDF

### 1.5.6 - April 20th

* Apryse core update to 9.0
* `TRN_ENABLE_AUTH_SESSION` no longer relies on cookies and now instead uses a query parameter, this

should prevent problems stemming from third party cookies. This updated scheme requires the latest WebViewer update as of this release. Requires WebViewer 8.0

* Added error handling to prevent leftover temporary files
* Fixed remote execution vulnerability through uploading of bad formats
* Removed old .jsp APIs
* Fixed issue with EML file paths preventing conversion when a blob is uploaded
* \[Windows] Updated LibreOffice and moved away from the portable scheme in exchange using a normal installer.
* Improved font support

### 1.5.5 - February 9th

* Fixed security issue with LibreOffice document formats using OLE objects
* Upgraded Tomcat to 10.0.2
* Removed UrlRewriteFilter dependency
* Corrected issues loading documents with malformed text
* Added width scaling for HTML documents wider than the standard page size
* Added [TRN\_MAX\_CELL\_COUNT](/web/webviewer-server/wv-server-config.md#max-excel-cell-count) for controlling the maximum allowed cells that can be rendered on an excel document
* CAD document improvements for fonts, zooming and stability
* General document improvements for stability
* Fix for GetThumb API incorrectly returning progress lines in JSON return values


---

# 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-2021.md?ask=<question>&goal=<endgoal>
```

`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.
