Skip to main content
Participant
September 6, 2022
Question

Adobe Acrobat Chrome Extension doing multiple calls

  • September 6, 2022
  • 2 replies
  • 4641 views

We have an online application that is limiting the PDF download to only once.  We've found that users have been complaining of the attachment not being downloadable.  Further investigation showed that the issue is only happening when users are accessing their PDF via Chrome with the Adobe Acrobat Extension.  From what it looks like, the extension is doing multiple calls to the file thus resulting to the file not being accessible due to the limit.  Can you please check on this and see what can be done to mitigate such problems.  The only solution we ahve so far is to have users uninstall the extension and try to download their file again.

2 replies

Participant
October 20, 2025

I am experiencing this as well. While regression testing a new build of an Azure hosted database, I am now unable to download PDF reports in Chrome when I have the Adobe Extension installed. If I remove the extension I can download the PDF report without issue. I can also download without any issues on Edge and FireFox. What I have been told by support is "When a report is run, it (the extension) downloads the pdf to the browser, then it (the extension) deletes the pdf from the netforum server (database I am testing), then the adobe add-on attempts to pull the file from the server again instead of the user's machine." I'm happy to provide a screen recording of the behavior if that would be helpful.  

Meenakshi Negi
Community Manager
Community Manager
September 8, 2022

Hi Reynold Joy259869475mmi,

 

Thank you for reaching out.

 

Please elaborate on the term "limiting the PDF download to only once". Do you mean that you cannot download multiple PDFs at once?

Do you get any messages when trying to download the PDFs from that particular website?

Is it a public website? If yes, please share the link with us to replicate the behavior.

Please share the step-by-step workflow you use to download the PDF and the screen recording.

 

Thanks,

Meenakshi

Participant
September 8, 2022

Hey Meenakshi,

 

The application is limiting the download to only once, it's a security feature.   Unfortunately, it's a user-authenticated web application.

 

What we've seen is that when the user clicks on the link to download, the new tab opens (as expected) but we then see that the tab opens the extension and the same link is passed as a parameter in the url, something like -> chrome-extension://efaidnbmnnnibpcajpcglclefindmkaj/{{url}}.  And yes, we have confirmed that this is only happening on Chrome when the extension is present.

 

We are not sure how the extension or Chrome handles the PDF attachments, but it just recently caused issues.  What I'm theorizing is that something changed on how Chrome calls the extension where when it sees that the file downloaded is supported by the extension after accessing it, it then calls the extension to re-trigger the download via the extension.  Maybe what it was doing before is to download the file and then open it with the extension?  

 

Please let me know if there is anything else I can provide.

Participating Frequently
April 21, 2025

Hi anthony_7098,

 

Thank you for reaching out.

 

Please let us know if this happens when downloading PDF from a particular website. It would be helpful if you could share the website address and video of the complete workflow. We will get this checked. 

 

Thanks,

Meenakshi


Hi Meenakshi,

 

I'm also diagnosing an identical issue to the above.  We have a system whereby PDF content is generated and made available for download from our web server a single time, i.e. the content is deleted after the initial fetch.

 

We've observed the Adobe Acrobat Chrome Extension (v25.4.2.2) double-fetching the content, this leads to a user-facing 404 error.  These IIS logs show how our server receives two back-to-back request for the same URL (/files/reports/4762e24f82d9200b8d569355dfa98ca2.pdf), and the resulting 404 error on the 2nd request:

 

2025-04-21 17:16:31 W3SVC2 WS-TN2 192.168.101.129 GET /files/reports/4762e24f82d9200b8d569355dfa98ca2.pdf - 443 - 192.168.11.123 HTTP/1.1 Mozilla/5.0+(Windows+NT+10.0;+Win64;+x64)+AppleWebKit/537.36+(KHTML,+like+Gecko)+Chrome/135.0.0.0+Safari/537.36 ASP.NET_SessionId=vhnwocy2m2dbx55payi2ikww https://test.vertifi.com/vcp/re/re_ach_main.aspx test.vertifi.com 200 0 0 4970 833 66

2025-04-21 17:16:31 W3SVC2 WS-TN2 192.168.101.129 GET /files/reports/4762e24f82d9200b8d569355dfa98ca2.pdf - 443 - 192.168.11.123 HTTP/2.0 Mozilla/5.0+(Windows+NT+10.0;+Win64;+x64)+AppleWebKit/537.36+(KHTML,+like+Gecko)+Chrome/135.0.0.0+Safari/537.36 ASP.NET_SessionId=vhnwocy2m2dbx55payi2ikww - test.vertifi.com 404 0 0 1486 625 0

 

We've found a few tricks that we can use as a workaround, though we'd much prefer to see this fixed in the Extension, it should not be fetching the content more than once.

 

Our workarounds:

1. defer the file deletion at our server

2. enable short duration caching in browser

context.Response.Cache.SetExpires(DateTime.Now.AddSeconds(60));
context.Response.Cache.SetCacheability(HttpCacheability.Private);

 

I'd be more than happy to work with Adobe on this matter, I'm a US-based software developer, we have a number of clients affected negatively by this issue.

 

Kind regards,

Chris Smith

Vertifi Software, LLC