Uploaded image for project: 'JDK'
  1. JDK
  2. JDK-8187223

Long JNLP file is not parsed correctly and ends with javaws path

    Details

    • Subcomponent:
    • Resolved In Build:
      b01
    • CPU:
      x86_64
    • OS:
      windows_10

      Backports

        Description

        FULL PRODUCT VERSION :
        java version "1.8.0_144"
        Java(TM) SE Runtime Environment (build 1.8.0_144-b01)
        Java HotSpot(TM) 64-Bit Server VM (build 25.144-b01, mixed mode)

        ADDITIONAL OS VERSION INFORMATION :
        Microsoft Windows [Version 10.0.15063]

        A DESCRIPTION OF THE PROBLEM :
        We have a very long URL-path which is called incorrectly.
        After exactly 960 characters the path in which the javaws.exe resides is appended.

        That leads of course to the incorrect loading of the jnlp file -
        which is less than the allowed 2048 characters long.

        EXPECTED VERSUS ACTUAL BEHAVIOR :
        EXPECTED -
        The jnlp file send to the webserver should be complete.
        For example :

        http[s]://thisisaverylong.path/[…]/960th character961st character/…
        ACTUAL -
        This is the actual result which is sent to the webserver:

        http[s]://thisisaverylong.path/[…]/960th characterC:\Program Files\Java\jre1.8.0_144\bin\javaws.exe

        REPRODUCIBILITY :
        This bug can be reproduced always.

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  herrick Andy Herrick
                  Reporter:
                  webbuggrp Webbug Group
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  5 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: