IJ04787: MALFORMED ATTACHMENT LINKS FOR FILES IN EDGE BROWSER

APAR status

• Closed as program error.

Error description

• PROBLEM:
  When a link to a local file is rendered in a list of
  attachments, the
  file://mydomain/path/... URI format configured by our doclink
  system
  properties is being modified to exclude the "file:" prefix when
  using
  the Microsoft Edge browser.
  
  This results in links that look like //mydomain/path/file.jpg,
  and
  that are not compatible with the Edge browser, resulting in
  file not
  found errors.
  
  This issue does not affect other browsers (e.g. Internet
  Explorer 11).
  
  The cause is a section of code in the label component JSP file
  that
  checks for the presence of "Chrome" in the browser's User-Agent
  header, and if found, removes the initial four characters from
  the URI.
  Modifying this JSP file to make an exception when "Edge" is also
  found in the User-Agent string solves the problem.
  
  Other workarounds include forcing Edge to emulate IE 11 and
  using IE 11
  instead of Edge.
  
  This support request is to report the issue and inquire if
  there is a
  workaround that does not call for modifying Maximo files or
  limiting
  browser choice--and/or to suggest an official fix if
  appropriate.
  
  
  
  ================================================================
  =======
  ADDITIONAL DETAILS
  ================================================================
  =======
  
  
  ----------------------------------------------------------------
  -------
  System Properties for DOCLINK
  ----------------------------------------------------------------
  -------
  
  Paths have been sanitized.
  
  mxe.doclink.doctypes.defpath
   /myshare/path/default
  
  mxe.doclink.doctypes.topLevelPaths
   /myshare/path
  
  mxe.doclink.path01
   /myshare/path = file://mydomain/path
  
  mxe.doclink.path02
   \\mydomain\path=file://mydomain/path
  
  
  
  ----------------------------------------------------------------
  -------
  User-Agent Header
  ----------------------------------------------------------------
  -------
  
  The User-Agent header sent by the Microsoft Edge browser reports
  versions for a variety of other popular browsers (to override
  websites that erroneously assume the Microsoft rendering engine
  cannot handle modern features). Here is a sample.
  
  User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64)
  AppleWebKit/537.36 (KHTML, like Gecko) Chrome/58.0.3029.110
  Safari/537.36 Edge/16.16299
  
  Manually removing the "Chrome/58.0.3029.110" portion of the UA
  string
  using in-browser Developer Tools (F12) verifies the problem (and
  solves it, but only while the browser tab remains open).
  
   Edge : DevTools : Emulation (docs.microsoft.com)
   https://goo.gl/1Pzdns
  
  It is not possible to configure a different User-Agent string
  in Edge.
  
   Custom user agent string for Microsoft Edge
  (docs.microsoft.com)
   https://goo.gl/rwvbKh
  
  
  ----------------------------------------------------------------
  -------
  Attempted Fixes and Workarounds
  ----------------------------------------------------------------
  -------
  
  The simplest workaround is to use Internet Explorer 11 instead
  of Edge.
  
  Forcing Edge to emulate IE 11 for the Maximo domain solves the
  problem. Presumably this can be done by configuring Enterprise
  Mode.
  
   Use Enterprise Mode to improve compatibility
  (docs.microsoft.com)
   https://goo.gl/5zW7R7
  
  The webclient.ie.compatversion system property in Maximo
  appears to
  have no impact on emulation in Edge.
  
  Modifying the JSP file for the label component to exclude Edge
  when
  it sniffs for Chrome also works.
  
  
  ----------------------------------------------------------------
  -------
  EXAMPLE MODIFICATION TO JSP FILE
  ----------------------------------------------------------------
  -------
  
  \MaxRoot\applications\maximo\maximouiweb\
   webmodule\webclient\components\label.jsp
  
  Delivered (line 407):
  
   newlink=newlink.substring(5);
  
  Modified (line 407-408):
  
   if (request.getHeader("User-Agent").indexOf("Edge") == -1)
    newlink=newlink.substring(5);
  
  PERFORMANCE ISSUE: no
  
  STEPS TO REPRODUCE: see above
  
  CURRENT ERRONEOUS RESULT: Getting file not found error message.
  
  EXPECTED RESULT: Attached document should be found and
  displayed in Edge browser.
  
  ADDITIONAL INFO:
  
  ENVIRONMENT (SYSTEM INFO):
  Weblogic Application Server 12.2.1.2.0
  
  
  ----------------------------------------------------------------
  -------
  Version
  ----------------------------------------------------------------
  -------
  
  Tivoli's process automation engine 7.6.0.8
  Build 20170512-0100
  DB Build V7608-63
  

Local fix

• na
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * Edge browser users                                           *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * MALFORMED ATTACHMENT LINKS FOR FILES IN EDGE BROWSER         *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  

Problem conclusion

• Fixed in label.jsp
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  SYSTEM CONFIG

• Fixed component ID

  5724R46S1

Applicable component levels

• R760 PSY

     UP