New update is altering the PDF byte hash

Aspose.PDF Product Family
1

Hi Support,

We recently updated to the latest version of Aspose PDF and it seems that anytime a PDF is being processed through Aspose, it’s adding in a unique value in its metadata.

image.png (71.3 KB)

image.png (49.1 KB)

We make hashes of documents so that we don’t have to redo any extra processing for documents that match the hash but since you’re adding in some unique timestamp and also some kind of unique ID inside the document, every single document is going to be unique and removes our ability to use cached documents for a performance boost.

Is there a way to prevent this? This is critical to our business since a majority of our documents are redundant files and will cost us a fortune to process 100% of them 100% of the time now.

2

@RichColeman

To ensure a timely and accurate response, please attach the following resources here for testing:

  • Your input PDF.
  • Please attach the output PDF file that shows the undesired behavior.
  • Please attach the expected output PDF file that shows the desired behavior.
  • Please create a standalone console application (source code without compilation errors) that helps us to reproduce your problem on our end and attach it here for testing.

As soon as you get these pieces of information ready, we will start investigation into your issue and provide you more information. Thanks for your cooperation.

PS: To attach these resources, please zip and upload them.