Skip to content
← Adobe Acrobat in Browsers

How can we improve Acrobat in Browsers?

Adobe Acrobat in Browsers: Adobe Acrobat in Chrome

Categories

Regression in Adobe Acrobat Chrome extension - verified and reproducible

We believe we've identified a regression in the Adobe Acrobat Chrome extension reproducable in the recent 26.8.1.4 release.

Our web application generates PDF reports in response to an authenticated HTTP POST. (Not a GET)

The server returns the PDF successfully. However, when the Adobe extension is enabled, immediately after the successful POST, the browser performs an unexpected GET request to the same URL.

This GET fails because the endpoint is POST-only.

When the Adobe extension is disabled, the unexpected GET does not occur, and the application functions normally.

We have HAR files and server logs showing both cases. (extension enabled and extension disabled)

Can engineers investigate this. We are currently telling users of our app to turn off the extension (and then it works fine) Note: It has been working fine for the last 6 years with the Adobe Extension. This is a new behavor for an existing solution.

Happy to privately share a HAR trace showing the related GET, and access to a reproducible test case if required.

1 vote

We're glad you're here

Please sign in to leave feedback
Signed in as (Sign out)
Close
Close

We’ll send you updates on this idea

Raymond Davey shared this idea  ·   ·  Report…  ·  Admin →
How important is this to you?

We're glad you're here

Please sign in to leave feedback
Signed in as (Sign out)
Close
Close

We're glad you're here

Please sign in to leave feedback
Signed in as (Sign out)
Close
Close
Submitting...
An error occurred while saving the comment
  • Raymond Davey commented  ·   ·  Report

    I have one further diagnostic result which may be useful.

    In Chrome's DevTools for the Acrobat extension, under Extension Storage → Local, I found:

    'mimeHandlerEnabled = "true"'
    'mimeCohort = "master"'

    As a test, I changed only:

    'mimeCohort = "chromeMimeHandler"'

    I then repeated exactly the same POST-generated PDF report with Acrobat extension 26.8.1.5 still enabled.

    The problem disappeared and the PDF displayed correctly.

    So on the same machine, browser, extension version and application:

    'mimeCohort = "master"' → POST PDF triggers the additional GET and fails

    'mimeCohort = "chromeMimeHandler"' → POST PDF displays correctly

    There is one further potentially important observation: the change to 'mimeCohort' does not persist.

    If I reload the application page from which the report is generated, the Acrobat extension automatically changes 'mimeCohort' back from '"chromeMimeHandler"' to '"master"'. Once it has reverted to '"master"', the original problem returns.

    So '"chromeMimeHandler"' is only a temporary diagnostic change. Something in the normal extension/page flow is actively setting the cohort back to '"master"'.

    This appears to provide a reproducible A/B test of the problem without changing the application, browser or extension version.

    Hopefully this gives the engineering team a useful pointer as to where the regression may be occurring.

  • Raymond Davey commented  ·   ·  Report

    Further note. I have just tested the same machine with the Edge browser.

    This extension works fine in Edge. Extension version 26.7.1.0

    I do note that this is an older version of the extension. The most recent update is not available in the Edge browser store

    I compared HAR captures between the working and failing versions.

    Adobe extension 26.7.1.0 in Edge: the POST receives a 200 application/pdf response and no further request is made to the PDF URL. The PDF displays correctly.

    Adobe extension 26.8.1.5 in Chrome: the same POST receives a 200 application/pdf response, but immediately afterwards a new GET request is made to the identical POST-only URL. That GET fails.

    This suggests a possible change/regression in how 26.8.1.5 handles PDFs returned directly from POST requests.

  • Raymond Davey commented  ·   ·  Report

    Version 26.8.1.5 does not fix the issue

    I have a clean HAR file for you if you contact me directly

    Can also set you up with a test case (in a live system) for you to diagnose

    All other extensions are disabled. This is a clean browser session under Chrome

  • AdminGaurav Chhabra (Admin, Adobe) commented  ·   ·  Report

    Hi,

    Thank you for using the Adobe Acrobat extension and for taking the time to report this issue. We sincerely apologize for the regression and appreciate the detailed information you shared, it has been very helpful.

    We recently published version 26.8.1.5 of the Acrobat Chrome extension to the Chrome Web Store, which includes a fix for a similar issue. Could you please update to version 26.8.1.5 and let us know whether the issue is resolved?

    You can update the extension by following these steps:

    1. Navigate to chrome://extensions.
    2. Enable the Developer mode toggle in the top-right corner.
    3. Click the Update button.
    4. Verify that the Acrobat extension has been updated to version 26.8.1.5.

    If the issue still persists after updating, we'd be happy to connect with you to better understand your environment, investigate the behavior further, and work towards a resolution. If you're available, please let us know a convenient time for a quick call or screen-sharing session.

    Thank you again for bringing this to our attention. We appreciate your patience and look forward to your update.

    Regards,
    Gaurav