C
chris
Client page: <input type="file".....>
Server: Apache, OC4J, J2EE app
XP, SP1 and updates
Works perfectly under HTTP.
However, under HTTPS the user needs to hit the submit button really
fast to
avoid a "page cannot be displayed". All other interaction with the
application works well.
As a workaround one can set the http-connection on the server as
use-keep-alives = "false" or increase the
oracle.j2ee.http.socket.timeout.
In my opinion this is a bug in IE as the browser does not make contact
to
the server before displaying the error. I do not see this bug in the
buglist
of IE.
Does anyone else has experienced the above?
Server: Apache, OC4J, J2EE app
XP, SP1 and updates
Works perfectly under HTTP.
However, under HTTPS the user needs to hit the submit button really
fast to
avoid a "page cannot be displayed". All other interaction with the
application works well.
As a workaround one can set the http-connection on the server as
use-keep-alives = "false" or increase the
oracle.j2ee.http.socket.timeout.
In my opinion this is a bug in IE as the browser does not make contact
to
the server before displaying the error. I do not see this bug in the
buglist
of IE.
Does anyone else has experienced the above?