ITW probes https first

[Jiri Vanek]

I had posted a patch for this. Feel free to review.
On 11/1/18 7:04 PM, Bernd Eckenfels wrote:
> Hello,
> 
>  
> 
> thank you Jiri, the noenforce did the trick.
> 
>  
> 
> However I wonder if this can be made a bit smarter. In my case there is no way that switching https
> for http would have worked since a non-default port was specified.
> 
>  
> 
> http://localhost:10000 -> https://localhost:8443 (maybe https://localhost/)
> 
>  
> 
> It would work in these cases:
> 
>  
> 
> http:/localhost -> https://localhost
> 
> http://localhost:80 -> https://localhost
> 
>  
> 
> I think the Scenarios where the same port would support both protocols is rather seldom, so only
> when no port is specified the enforce could work ist magic. Changing that would reduce the Need for
> manual reconfiguration.
> 
>  
> 
> Alex, for ojdkbuild I could imagine that setting that as a default causes less trouble for people
> Looking to relace Oracle Web Start (which does not have this Problem). (especially given there is no
> itw-settings available)
> 
>  
> 
> Gruss
> 
> Bernd
> 
> -- 
> http://bernd.eckenfels.net
> 
>  
> 
> *Von: *Jiri Vanek <mailto:jvanek at redhat.com>
> *Gesendet: *Donnerstag, 1. November 2018 10:30
> *An: *Alex Kashchenko <mailto:akashche at redhat.com>; distro-pkg-dev
> <mailto:distro-pkg-dev at openjdk.java.net>
> *Cc: *Bernd Eckenfels <mailto:ecki at zusammenkunft.net>
> *Betreff: *Re: Fwd: ITW probes https first
> 
>  
> 
> itweb-settings.sh -verbose | grep https
> 
>     deployment.https.noenforce                        - false (Possible: are true or false)
> 
>     deployment.proxy.https.host                       - null
> 
>     deployment.proxy.https.port                       - null
> 
>  
> 
>  
> 
>  
> 
> Yes, itw is enforcing https first. If it is making troubles, please set deployment.https.noenforce
> 
> to true in your properties file.
> 
>  
> 
> The reasoning is, that many legacy javaws apps are still linked as http, while being already
> 
> redeployed on well established https server.
> 
>  
> 
>  
> 
> J.
> 
> On 10/31/18 10:15 PM, Alex Kashchenko wrote:
> 
>> Hi,
> 
>>
> 
>> Forwarding from ojdkbuild list, AFAIU the problem is not specific to ojdkbuild launcher.
> 
>>
> 
>> ITW seems to try "https://" URL first and if HTTPS connection hangs that causes problems.
> 
>>
> 
>> -------- Forwarded Message --------
> 
>> Subject: ITW probes https first
> 
>> Date: Tue, 30 Oct 2018 12:33:17 -0700 (PDT)
> 
>> From: Bernd Eckenfels <ecki at zusammenkunft.net>
> 
>> To: ojdkbuild <ojdkbuild at googlegroups.com>
> 
>>
> 
>> When I start javaws.exe from the command line (or use a java.exe command line) I notice that with my
> 
>> application ITW takes very long to start with the download.
> 
>> I copied the full comand line from the launcher, adding -verbose and noticed the following:
> 
>>
> 
>> It takes long as it tries to connect with https first (and since its a http server it probably hangs
> 
>> in the handshake):
> 
>>
> 
>> "C:\Program Files\ojdkbuild\java-1.8.0-openjdk-1.8.0.191-1\bin\java.exe" > -XX:MinHeapFreeRatio=20
> 
>> -XX:MaxHeapFreeRatio=40 -splash:"C:/Program >
> 
>> Files/ojdkbuild/java-1.8.0-openjdk-1.8.0.191-1/webstart/javaws_splash.png" >
> 
>> -Xbootclasspath/a:"C:/Program > Files/ojdkbuild/java-1.8.0-openjdk-1.8.0.191-1/webstart/javaws.jar"
> 
>>> -classpath "C:/Program > Files/ojdkbuild/java-1.8.0-openjdk-1.8.0.191-1/jre/lib/rt.jar" >
> 
>>
> -Ditw.userdata="C:/User/AppData/Local/ojdkbuild/java-1.8.0-openjdk-1.8.0.191-1.b12.ojdkbuild.windows.x86_64/webstart/"
> 
>>> -Dicedtea-web.bin.name=javaws.exe -Dicedtea-web.bin.location="C:/Program >
> 
>> Files/ojdkbuild/java-1.8.0-openjdk-1.8.0.191-1/webstart/javaws.exe" >
> 
>> net.sourceforge.jnlp.runtime.Boot -Xnofork -verbose > http://127.0.0.1:10000/app/frontend.jnlp
> 
>>> ...
> 
>>> All possible urls for location=http://127.0.0.1:10000/app/frontend.jnlp state=PRECONNECT
> 
>>> CONNECTING PREDOWNLOAD PROCESSING : [https://127.0.0.1:10000/app/frontend.jnlp,
> 
>>> https://127.0.0.1:10000/app/frontend.jnlp, http://127.0.0.1:10000/app/frontend.jnlp,
> 
>>> http://127.0.0.1:10000/app/frontend.jnlp]
> 
>>> Connecting https://127.0.0.1:10000/app/frontend.jnlp
> 
>>> Adding
> 
>>> sun.net.www.protocol.https.DelegateHttpsURLConnection:https://127.0.0.1:10000/app/frontend.jnlp
> 
>>> done https://127.0.0.1:10000/app/frontend.jnlp
> 
>>> ...
> 
>>> Browser selected proxies: [DIRECT]
> 
>>> Selected proxies: [DIRECT]
> 
>>> 
> 
>>
> 
>> When its downloaded its not much faster unless i specify the -noupdate option.
> 
>>
> 
>> Any idea why it is doing that and how to avoid it? It does not help to specify "-jnlp http://.." or
> 
>> "jnlp://.." as the url.
> 
>>
> 
>> Gruss
> 
>> Bernd
> 
>>
> 
>>
> 
>>
> 
>  
> 
>  
> 
> -- 
> 
> Jiri Vanek
> 
> Senior QE engineer, OpenJDK QE lead, Mgr.
> 
> Red Hat Czech
> 
> jvanek at redhat.com    M: +420775390109
> 
>  
> 


-- 
Jiri Vanek
Senior QE engineer, OpenJDK QE lead, Mgr.
Red Hat Czech
jvanek at redhat.com    M: +420775390109