Acrobat Chrome extension blocks valid PDFs served from Greenbook API endpoints — ERR_BLOCKED_BY_CLIENT
PROBLEM
The Adobe Acrobat extension for Google Chrome fails to open a publicly accessible PDF delivered through an API endpoint, producing ERRBLOCKEDBY_CLIENT.
Chrome's native PDF viewer opens the identical URL successfully, and the Acrobat extension can render the same PDF after it is downloaded locally.
PUBLIC REPRODUCTION URL
https://www.greenbook.net/api/products/53534/documents/2307/view
This is a publicly accessible 45-page Bayer Luna Sensation product label. No login or authentication is required.
ENVIRONMENT
Operating system: Windows 11
Browser: Google Chrome, updated
Adobe Acrobat desktop application: Updated
Acrobat Chrome extension: Originally 26.10.2.2, subsequently updated
Extension site access: On all sites
Acrobat preference "Online PDFs": Enabled when reproducing the failure
STEPS TO REPRODUCE
Enable the Adobe Acrobat extension in Chrome.
Under Acrobat extension preferences, enable "Online PDFs" so Acrobat automatically handles online PDFs.
Navigate directly to the public Greenbook URL above.
Chrome displays "www.greenbook.net is blocked" with ERRBLOCKEDBY_CLIENT.
EXPECTED RESULT
The PDF should open in the Adobe Acrobat extension, just like other online PDFs.
ACTUAL RESULT
The browser displays ERRBLOCKEDBY_CLIENT rather than opening the document.
CONTROLLED TEST RESULTS
Acrobat enabled with Online PDFs enabled: FAILS
Acrobat extension completely disabled: WORKS
Acrobat enabled but Online PDFs disabled: WORKS in Chrome's native PDF viewer
Downloaded Greenbook PDF opened locally: WORKS in the Acrobat extension
Official Adobe Acrobat extension test PDF: WORKS
New, clean Chrome profile: FAILS identically
Chrome, Acrobat desktop application, and extension updated: Still fails
NETWORK EVIDENCE
Chrome DevTools captured the Greenbook endpoint returning:
HTTP Status: 200 OK
Content-Type: application/pdf
Content-Length: 282759 bytes
Content-Disposition: inline; filename="Specimen Label.pdf"
Content-Security-Policy: sandbox; frame-ancestors 'none'
Server: istio-envoy
The HTTP request completed successfully in approximately 153 ms.
The original URL does not end in ".pdf", although the server correctly identifies the content as a PDF and provides a PDF filename.
EXTENSION CONSOLE ERROR
Uncaught (in promise) Error: Could not establish connection. Receiving end does not exist.
This error was observed in the extension console. Its relationship to the PDF-opening failure has not been established.
WORKAROUND
Disabling "Online PDFs" under Acrobat extension preferences restores access to Greenbook PDFs through Chrome's native viewer while keeping the Acrobat extension enabled.
Alternatively, users can download the document from Greenbook and open the downloaded file in Chrome, where Acrobat handles it successfully.
Neither workaround restores automatic online PDF handling by Acrobat.
RELATED ADOBE ISSUE
A potentially related issue involving PDFs delivered through dynamic application endpoints was previously reported:
Adobe previously addressed similar behavior in version 26.8.1.6. Our tests demonstrate related symptoms with a more recent extension.
REQUEST
Please investigate whether Acrobat's automatic PDF interception mishandles PDFs served from extensionless API endpoints, or whether the response security headers interfere with the extension.
The provided URL is public and reproducible without customer credentials.
We can provide additional screenshots, sanitized HAR captures, and extension diagnostics if needed.
Thank you for investigating.