The dialogs doesn't show up over HTTPS connection.

JWS usually shows Version check and Launching dialog when it start up.

But when it started over HTTPS connection, those dialogs doesn't show up.

When we use HTTP connection, the application launch by following step.

1. Java loading dialog shows

2. Version check dialog shows

3. Launching application dialog shows

4. Application launched

However, in the case of HTTPS connection, step2, 3's dialog doesn't show up.

(It might be skipped? What's going on?)

I think that the step1,2,3 are processed by JavaWebStart.

Is there any way to show these dialogs when we use HTTPS connection?

Client: Windows XP(SP2), JDK: 1.4.2_06

Web Server: WebLogic(ver.8.1)

[732 byte] By [akikoa] at [2007-10-2 3:17:50]
# 1
I think your application is already cached, that's why you are not seeing those dialogs. Can you try clearing the cache and then re-launch the application using the HTTPS connection...-Cheran
baratha at 2007-7-15 21:45:12 > top of Java-index,Desktop,Deploying...
# 2

Hi,

Sorry, I should write more information.

Version check and Launching dialog doesn't show up when

there's no updated jar at the server over HTTPS connection.

When I download the application at the first time, those dialogs appears.

And also, if there's updated jar at the server, dialogs show up.

(so, when I clean caches and re-launcht the application, I can see dialogs.)

When I download the application over HTTP connection,

I see Version check and Launching dialogs every time.

(it doesn't matter if there's updated jar or not)

JWS does check updates over HTTPS connections, so it

supposed to show those dialogs...but it doesn't...

akikoa at 2007-7-15 21:45:12 > top of Java-index,Desktop,Deploying...
# 3

When running over http or file protocol, these dialogs are shown if the update check takes more than 1500 ms, when application must be updated before launching (due in 1.5.0 to offline-allowed not being specified, or setting <update check="always" /> in 6.0) (assuming target isn't using basic authentication). If the update check can complete in less time than that, then the dialogs will not be shown.

For https, there is a probability that the attempted https connection will cause https security dialogs, which would then always cause the check to take more than 1500 seconds (or whatever timeout is configured) so webstart won't show the download progress dialog untill it knows there is an update.

This should be a bug, since it is handled beter in BasicAuthentication case.

If you are using Authentication, the download dialog will show up only after 1500 ms if the JAuthenticator chalange dialog is not being shown.

Similarilly, using https, he dialog should show after 1500 ms (or whatever timeout) if the https security dialog, or host mismatch dialog is not showmin.

/Andy

dietz333a at 2007-7-15 21:45:12 > top of Java-index,Desktop,Deploying...
# 4

Hi,

Over HTTPS connection, it takes about 25sec until my application completely launch.

I don't know how long does JWS take time to check updates, but I think it takes more than 1500ms.

In the case of HTTP, application launch faster than HTTPS connection (about 20sec).

However, it shows Version check dialogs.

>Similarilly, using https, he dialog should show after 1500 ms (or whatever timeout)

>if the https security dialog, or host mismatch dialog is not showmin.

I tried this. I made the case "https security dialog is not be shown".

I selected "allow this access always" at the security dialog, so it won't ask next time I download.

But, still I can't see version check dialog... :(

/akiko

akikoa at 2007-7-15 21:45:12 > top of Java-index,Desktop,Deploying...
# 5
Does anyone have ever seen the version check dialog("Checking for latest version") over HTTPS connection...? /akiko
akikoa at 2007-7-15 21:45:12 > top of Java-index,Desktop,Deploying...