Oleg
Thank you for your advice. Some modules offered by a software vendor
depends on Tomcat 3.2.x, so I'm compelled to use. I tried FileUpload on
Tomcat 4.1.18 with SSL and it worked fine! I'll try with Apache + Tomcat
3.2.4 later. It seems that the factor of the problem is at server side.
Thanks
rence.
Cheers
Oleg
-Original Message-
From: TANAKA Yuui [mailto:[EMAIL PROTECTED]
Sent: Freitag, 7. März 2003 09:32
To: Commons HttpClient Project
Subject: Re: Problem with MultipartPostMethod via HTTPS
Thank you for your quick reply.
I tried the latest HttpClient from CVS, but failed
Thank you for your quick reply.
I tried the latest HttpClient from CVS, but failed. And I did on another
machine, then I got the same result. As you point out the problem may be
occurred in the server side. The processing library for file upload is
Jakarta Commons FileUpload 1.0 and I run it on To
I'm not exactly sure what's going wrong here. It seems that the
connection is being closed/reused on the either the client or server
side before the entire response is read. I tried your code on my
machine at home and it worked well. I am guessing the problem is
either with the version o
Sorry, the code I wrote in my previous post is just an example I edit.
Here is the real code:
public class Main {
String host = "192.168.0.52";
String scheme = "https";
int port = 443;
String fileSendUrl = "/order/test";
Multipart posts with SSL should work. The only strange thing I noticed
in your example is that the file part is never added to the post
method. Is this what's happening in the real code? If so, this could
be the source of the problem. If not, a wire log of the problem would
help. Take
I tried to send a file to a servlet with MultipartPostMethod via HTTPS,
then I get:
java.net.SocketException: Connection reset
at java.net.SocketInputStream.read(SocketInputStream.java:168)
at com.sun.net.ssl.internal.ssl.InputRecord.a(DashoA6275)
at com.sun.net.ssl.intern
