OpenPDF | .Net Standart PDF reading library | Document Editor library

I found the solution , it was simply that the web service's client should precise the response type as array buffer , In my case it was VueJS , so i added the following on axios call :

Your code does not contain any return statement. Laravel offers a variety of ways to make responses.

https://laravel.com/docs/8.x/responses

For example, a file response.

For a clean solution you need to use the PdfWriter instance, so first replace

Flying-saucer doesn't support Flex, and will likely never support it.

The CSS supported by flying-saucer is limited to CSS 2.1 and most of CSS paged media.

If it does not work with Safari specifically, it is more of a browser support issue and not your code specifically.

You may need to narrow down the issue to check where this one is coming from, tools like Browserstack can help to find out the version from which it may work again.

Then, it comes down to see if you can find a polyfill to replicate the unsupported snippet of code.

Edit: Answer not relevant after your latest edit to question.

If you're going to use external storage, here's how to do it:

Your question essentially is not about OpenPDF in particular but about certain values in the DocMDP transform dictionary. Thus, my answer will not be focused on OpenPDF.

In PDF versions 1.5 and 1.6 so-called Object Digests were used in addition to the Byte Range Digests in signatures with transform methods. These digests were calculated recursively over a certain set of PDF objects depending on type and parameters of the transform in question.

The DigestMethod value is the hash algorithm to use in object digests.

In Adobe's PDF Reference 1.7 object digests were deprecated which was made really clear in the errata:

In ISO 32000-1 object digests were completely removed from the text (in some cases leaving text behind which is difficult to understand).

Thus, the values you are wondering about are deprecated and are not to be used for verification purposes anymore.

You also find the reason why iText uses dummy values in the same errata:

Thus, Adobe Acrobat 7 and 8 required some values to be there. Nowadays there is no need for them anymore.

In this context you may be interested in the PDF issue 117 - the DigestMethod had erroneously become required in ISO 32000-2:2020 and this issue is about deprecating it.

In ASP.NET Core you can return an VirtualFileResult

A FileResult that on execution writes the file specified using a virtual path to the response using mechanisms provided by the host.

Or you can do a Server.MapPath("~/pdf/light.pdf") to get the virtual path.

Returns the physical file path that corresponds to the specified virtual path.

In your example code you would use it as such:

I finally found a solution. I can't say it's a best solution but it works perfectly.