Merge XFDF API giving [502] Internal error

Bug Reports
1

We are suddenly receiving 502 errors when sending a request to the Merge Xfdf endpoint.

Access to fetch at ‘https://api.pdfjs.express/xfdf/merge’ from origin ‘’ has been blocked by CORS policy: No ‘Access-Control-Allow-Origin’ header is present on the requested resource. If an opaque response serves your needs, set the request’s mode to ‘no-cors’ to fetch the resource with CORS disabled.

Identical requests have been working until this point.

2 Likes
3

Hello reva,

How are you calling the API?
I will contact the developers to look into the API

Thank you,
Tyler

1 Like
4

Thank you.

We are using the recommended utility package to call the API. See below

import ExpressUtils from "@pdftron/pdfjs-express-utils";
const expressUtils = new ExpressUtils({
  clientKey: OUR_CLIENT_KEY,
});

...

const fileData = await documentViewer.getDocument().getFileData({});
const blob = new Blob([fileData], { type: "application/pdf" });
expressUtils.setFile(blob);

const xfdf = await annotationManager.exportAnnotations();
expressUtils.setXFDF(xfdf);

const response = await expressUtils.merge(); // merge XFDF

const mergedFile = await response.getBlob();
5

Hi Tyler,

We have the same problem, 502 errors when sending requests to Merge XFDF.

6

Hi Tyler,

We have the same problem.
When will this problem be resolved?

7

Hi there - noticing the same problem here. Calls to https://api.pdfjs.express/xfdf/set are giving 502 internal server error since earlier today. In my case this is using PHP Curl.

8

I’ve encountered the same difficulty: 502 errors when sending requests to Merge XFDF. Please fix this issue as a priority.

9

I’ve encountered the same difficulty: 502 errors when sending requests to Merge XFDF. Please fix this issue as a priority.

1 Like
10

We are getting the same error also

11

Same error here starting yesterday. It’s even happening on the demo page.

Capture
Capture1244×686 96.3 KB

12

same error . production is blocked. getting complaints

13

We are still encountering this error for almost 24 hours at this point. We use this API in production and a resolution is critical. Is there any timeframe for when this will be addressed?

14

Hello,

Our sincere apologies, we have discovered the source of the issue on the server and have fixed it.

Best regards,
Tyler

1 Like
15

Thank you for resolving this