- 
    Type:
Bug
 - 
    Resolution: Fixed
 - 
    Priority:
  P3                     
     - 
    Affects Version/s: 8u144, 9
 - 
    Component/s: deploy
 
- 
        b01
 - 
        x86_64
 - 
        windows_10
 
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build | 
|---|---|---|---|---|---|---|
| JDK-8212345 | 8u202 | Andy Herrick | P3 | Resolved | Fixed | b01 | 
| JDK-8207652 | 8u192 | Andy Herrick | P3 | Resolved | Fixed | b02 | 
| JDK-8202219 | 8u181 | Andy Herrick | P3 | Resolved | Fixed | b04 | 
| JDK-8211572 | emb-8u191 | Andy Herrick | P3 | Resolved | Fixed | master | 
| JDK-8203076 | emb-8u181 | Andy Herrick | P3 | Resolved | Fixed | b04 | 
                    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.
            
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.
- backported by
 - 
                    
JDK-8202219 Long JNLP file is not parsed correctly and ends with javaws path
-         
     - Resolved
 
 -         
 - 
                    
JDK-8203076 Long JNLP file is not parsed correctly and ends with javaws path
-         
     - Resolved
 
 -         
 - 
                    
JDK-8207652 Long JNLP file is not parsed correctly and ends with javaws path
-         
     - Resolved
 
 -         
 - 
                    
JDK-8211572 Long JNLP file is not parsed correctly and ends with javaws path
-         
     - Resolved
 
 -         
 - 
                    
JDK-8212345 Long JNLP file is not parsed correctly and ends with javaws path
-         
     - Resolved
 
 -