Support Article
Empty requestors created while opening PDF document
SA-53421
Summary
PDF document opens in a pop-up window using ContentDisposition inline. Opening the PDF in the Edge browser, creates and documents empty requestors in Autonomic Event Services (AES) or System Management Application (SMA).
Error Messages
Not Applicable
Steps to Reproduce
1. Retrieve a document from an external source and capture it in a byteArray as below,
//Get the byte array from the parameter page
byte[] byteArray=(byte[])tools.getParameterPage().getParameterValue("FileBinaryContent");
String fileName = (String) tools.getParameterPage().getParameterValue("FileName");
// create custom HTTP headers
HashStringMap aMap = new HashStringMap();
aMap.put("ContentDisposition", "inline;filename=\"" + fileName+ "\"");
aMap.put("ContentType", "application/force-download");
aMap.put("ContentType", "application/octet-stream");
aMap.put("ContentType", "application/download");
//Send the PDF File back to the user.
String result=tools.sendFile(byteArray,fileName,false,aMap,true);
2. Open the document from the Microsoft Edge browser. New empty requestors are created and noted in the SMA.
Root Cause
A third-party product issue. Edge browser makes a dual request to the server.
Resolution
Here’s the explanation for the reported behavior:
The Edge browser makes a dual request for an inline PDF. That is, the browser sends the first request after which the viewer initiates the second.
Published July 23, 2018 - Updated October 8, 2020
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.