Skip to main content

IE 11 problem workaround - file names messed up


Note: patch 18277370 needed for 11.1.1.7 to run ie 11

All our download links on ie 11 file names looked like they have been url encoded something like:

UTF-8_Q_Bobs=5FBooks=2Epdf=

Really irritating for our users so the quick and dirty for now was to modify (luckily all our download code is common) our download method to reset the headers on the response.



On our button we add the following:
<af:fileDownloadActionListener filename="test.txt"
    contentType="application/octet-stream"
    method="#{bean.startDownload}"/>


And we add a property to the request that contains the ucm path like such:
  <af:setPropertyListener from="/ucm/path/here"
                                      to="#{requestScope.ucmCurrentDocument}"
                                      type="action"/>

    public void startDownload(FacesContext facesContext, OutputStream outputStream) {
        String docName = (String)JSFUtils.getFromRequest("ucmCurrentDocument");
        applyIE11Fix(docName);
 ... write file to output stream here ...
    }


    private void applyIE11Fix(String docName) {
        RequestContext requestCtx = RequestContext.getCurrentInstance();
        Agent agent = requestCtx.getAgent();
        String version = agent.getAgentVersion();
        String browser = agent.getAgentName();

        //if ie 11
        if (browser != null && "ie".equals(browser) && version != null && version.startsWith("11")) {

            HttpServletResponse resp = JSFUtils.getResponse();
            String finalName = docName;

            try {
                finalName = URLEncoder.encode(docName, "UTF-8");
            } catch (UnsupportedEncodingException e) {
            }

            resp.setHeader("content-disposition", "attachment; filename=\"" + finalName + "\"");
            resp.setContentType("application/octet-stream");
        }
    }



Comments

  1. ¿What is ucmCurrentDocument?
    I'm trying to replicate your code.
    but I know no, how interpret this part:
    Row docName = (Row)JSFUtils.getFromRequest("ucmCurrentDocument");

    you could help me please...

    The patch 18277370 was affixed in weblogic 11g and I'm using Jdeveloper Version 11.1.1.7.0.

    ReplyDelete
    Replies
    1. I have updated the post as I was not clear. It is the document location passed in from the button via the request using a setPropertyListener

      Delete

Post a Comment

Popular posts from this blog

ADF sort of generic screen for tables with the same structure

We have a couple (about a hundred) of tables with the same structure (Code, Description, Create Date, Update Date). So I wanted to do something simple so that I did not have to create all these screens 1) EO   I created the EO based on one of the tables I had that had the above columns. I then Added a transient attribute called table name to my EO based on a groovy expression. (the expression needs to change as I am reading web tier stuff from the model layer but I will fix this later) I then generated a java class for my EO. And added the following overriden method to my newly created java class. protected StringBuffer buildDMLStatement(int i, AttributeDefImpl[] attributeDefImpl,   AttributeDefImpl[] attributeDefImpl2, AttributeDefImpl[] attributeDefImpl3, boolean b) {   StringBuffer statement = super.buildDMLStatement(   i, attributeDefImpl, attributeDefImpl2, attributeDefImpl3, b); return new StringBuffer(StringUtils.replace(statement.to...

Util code

public static MethodExpression getMethodExpression( String expr, Class returnType, Class[] argTypes){ FacesContext fc = FacesContext.getCurrentInstance(); ELContext elctx = fc.getELContext(); ExpressionFactory elFactory = fc.getApplication().getExpressionFactory(); return elFactory.createMethodExpression( elctx, expr, returnType, argTypes); } public static javax.faces.el.MethodBinding getMethodBinding( String expr, Class[] argTypes){ FacesContext fc = FacesContext.getCurrentInstance(); ELContext elctx = fc.getELContext(); return fc.getApplication().createMethodBinding(expr, argTypes); } SetPropertyListener listener = new SetPropertyListener( ActionEvent.class.getName()); listener.setFrom(link.getRoute()); listener.setValueExpression("to", JSFUtils.getValueExpression("#{pageFlowScope.route}", String.class)); action.addActionListener(listener); AdfFacesContext.getCurrentInstance().getPageFlowScope() .put("route", lin...

MANIFEST.MF merge JDeveloper for an executable jar

Goto your project > properties. Then click on deployment in the menu. Edit or add a jar deployment profile. Fill in the details under jar options (select Include manifest and give it a main class name) Also remember that the merge functionality only works with a BLANK line at the end of the merge file. REALLY this caught me. My merge file contents: Class-Path: commons-codec-1.3.jar [...empty line here CRLF...]