Gzip Cache Configuration
Configure the Rasterex Engine patch, gzip cache folder, IIS response header, and cache refresh.
Use this procedure when Rasterex Support has supplied the Rasterex Engine patch and instructed you to enable gzip responses for the RxBinWeb gzip endpoint. It is an installation and server-configuration procedure, not an NPM or Canvas SDK configuration.
The patch URL and the installed Engine/IIS paths must match the deployment instructions supplied for your release. The paths below are the documented 4.3.x layout; confirm them on the target server before changing files.
- Back up rxcsisapi.ini before editing it.
- Use an Administrator account and schedule a short IIS interruption.
- Do not apply Content-Encoding: gzip unless the gzip endpoint returns gzip-compressed content.
Download and install the patch supplied for the deployment. The current support-provided patch reference is shown below; confirm that it is the intended patch before running it.
- Run the MSI as Administrator.
- Complete the installation before editing the Engine configuration.
In the installed Rasterex Engine bin directory, create a folder named gzip. Confirm the actual installation root on the server before creating the folder.
Open the existing rxcsisapi.ini file and update the [CACHE] and [AutoCAD] sections. If either section already exists, update or add only these values. Leave licensing and unrelated configuration unchanged.
- Save a backup copy before editing.
- Confirm the cache and gzip directories exist after saving.
In IIS Manager, select the RxBinWeb gzip application or virtual directory documented for the deployment. Open HTTP Response Headers and add the following header. If the current IIS layout uses a different site or application name, stop and confirm the correct mapping before applying it.
- Apply the change.
- Verify that the endpoint serves gzip-compressed responses; do not use this header for uncompressed files.
After the configuration is saved, clear the contents of the Engine cache so previously generated responses do not mask the new configuration. Keep the cache folder itself.
Restart the relevant IIS site or application pool after the configuration and cache changes. If the deployment requires a full IIS restart, run the following command from an elevated PowerShell prompt and confirm that IIS reports a successful restart.
Open the affected AutoCAD/DWG file again and confirm that the original issue is resolved. Record the patch version, Engine path, configuration change, and test result for support or rollback purposes.
- The affected file opens successfully.
- The gzip endpoint returns a valid response with the expected Content-Encoding behavior.
- No unrelated IIS site or application is unavailable after the restart.
- The previous rxcsisapi.ini backup remains available if rollback is required.
