Merge API returning 500 error response

Technical Support
1

Which product are you using?

PDF.js Express Plus

PDF.js Express Version

8.7.5

Detailed description of issue
For some of our users, when attempting to use the merge API endpoint in Chrome / Edge, they are receiving a 500 error response stating “Server-side request must use server-side key”. This API call is initiated from the frontend client side and we are passing the correct key through to the API.

We are unable to replicate this behavior locally when debugging this.

When researching this issue, it sounds very similar to XFDF Merge API giving a 500 internal server error - Server-side request must use server-side key but I was wondering if there’s anything else that can be done to mitigate this issue? I cannot confirm right now that our users are using a proxy or VPN.

Expected behaviour
The merge call should succeed and return the appropriate PDF merged with annotations.

Does your issue happen with every document, or just one?
For the users that are experiencing the issue, it is happening for all of their documents.

Link to document
{Provide a link to the document in question if possible}

Code snippet
{Provide a relevant code snippet}

3

Hello jon.anders,

How are you supplying the key?

If this only works locally, but not on production, it could be how the key is added. If its done through env variables, then double check if the key is being correctly retrieved.

Best regards,
Tyler

4

This is happening in a production setting. I’ve verified we are passing the correct license key (for production use) and also the client key to the API.

5

Hello jon.anders,

Unfortunately theres not much information for me to go off of, since youre unable to reproduce this locally and cant confirm if they have a proxy or VPN.

The best I can suggest is that the user tries to load it outside of their network and using another computer to confirm if its their network or computer.

Best regards,
Tyler