PDF file viewer download exceeds the GET request character limit

[Dave Vandermark]

In our application the parameters needed to return certain PDF documents exceed the character limits for a GET request.  We are getting around this by performing a POST request when we originally get the file to show in the PDF viewer.  However, when the user tries to download the file they are seeing in the PDF viewer Chrome is making a GET request to try and get the file again.  This GET request fails causing the download the fail.  Currently our users can do Print > Save As, as a work around to download the file, but this isn't ideal.  

Is there some way the download can be set to use the file used for the preview, or set up to detect what type of request was used to get the file for preview and make that same type of request when doing the download?

[Bradley Cooper]

My organization is having the same problem.  Browsers such as Edge and IE have character limits on their URLs (and accordingly their GET requests), so we moved our security token to the header and use POST requests to retrieve resources (including PDFS).

The problem is that the Chrome PDF viewer insists on using a GET request when you click the download button.

Were you able to find a solution to this problem?

[Julian Pastarmov]

Please file this as a bug on https://crbug.com/ and it will make it faster to the responsible devs for triaging. You can post the bug number here too for anyone else looking for this information.