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

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...]

OJDeploy: Documentation for the tool

Real DOCS:  http://docs.oracle.com/cd/E26098_01/user.1112/e17455/deploying_apps.htm#OJDUG645 OJDeploy Documentation if you run it from the command line - I keep looking for this so I though I would post it here so I remeber. Oracle JDeveloper Deploy 11.1.2.1.0.6081 Copyright (c) 2003, 2010, Oracle and/or its affiliates. All rights reserved. Usage:   ojdeploy -profile <name> -workspace <jws> [ -project <name> ] [ <options> ]   ojdeploy -buildfile <ojbuild.xml> [ <options> ]   ojdeploy -buildfileschema Arguments:   -profile               the name of the Profile to deploy   -workspace      full path to the JDeveloper Workspace file(.jws)   -project              name of the JDeveloper Project within the .jws where the Profile can be...

JBO-25013: TooManyObjectsException

oracle.jbo.TooManyObjectsException: JBO-25013: Too many objects match the primary key oracle.jbo.Key[Key null ]. Ok so for you it may be trying to insert a duplicate record this should explain your problem (also check trigger they could be the cause.) NOTE: You can also try to create a new duplicate EO if you have a page with two VO's using the same EO. This could sort your problems. For me I needed to add a launch listener on my LOV and clear the cache of my vo. LOV <af:inputListOfValues id="NameId" popupTitle="#{bindings.Name.hints.label}" value="#{bindings.RolName1.inputValue}" label="#{bindings.RolName1.hints.label}" model="#{bindings.RolName1.listOfValuesModel}" required="#{bindings.RolName1.hints.mandatory}" columns="#{bindings.RolName1.hints.displayWidth}" shortDesc="#{bindings.RolName1.hints.tooltip}" launchPopupListener="#{backingBeanScope.backingBean.launchPop...