Did somebody implement multipart posting for uploading data to a server?
It's a part of any browser, so Netscape's one can be a source, but it's to
boring to look in their sources.
Dmitry.
----- Original Message -----
From: "Steven Owens" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, December 16, 1999 8:54 AM
Subject: Re: POSTing through sockets to an HTTPS server
> Dan,
>
> > I'm nearly finished with a class file that does an HTTPS post using
either
> > sockets or a URL object. The code will be finished today or tomorrow.
It
> > uses either Sun's JSSE or SSLJ from RSA to handle the secure
communication.
> > You'll need the RSA tools if you want to use JDK 1.1.x as JSSE only
works
> > with JDK 1.2.x.
> >
> > I'm using it for communicating with credit card processing companies
like
> > Skipjack IC and AuthorizeNet, but you could use the code to do an HTTPS
> > POST to any server you want.
>
> I'm interested in all of these topics. I started to research how
> to code a client for cybercash last year, but got sidetracked before I
> made significant headway. Cybercash's docs are (or at least were at
> the time) very fluffy and contentless.
>
> I'm also very curious about the SSL issue. How much does SSLJ
> from RSA cost? One thing I've been contemplating recently is that I'd
> really love to set up an SSL proxy server or packet sniffer that I can
> upload the browser and server certificates to, so it can decode the
> SSL, and then monitor the connection to troubleshoot new servlets.
> I've found that some browsers (in particular one emanating from
> Redmond) add quite a bit of flakiness when you add SSL into the
> exchange.
>
> Up until now, all of my java has been server-side, servlets, some
> RMI servers, etc. I've been working with the URL class a bit lately.
> One thing I find annoying is that there's no clear, simple way to
> indicate that I want to send a POST instead of a GET. It seems the
> only way to make the URL do a POST is by odd, indirect means. One
> source says use:
>
> URLConnection.setRequestProperty("Content-Type",
> "application/x-www-form-urlencoded" )
>
> Another source says to print to the output stream before reading
> from the input stream.
>
> Overall it feels like this whole collection of classes - URL,
> URLConnection, etc, is overly complicated. I realize that it's meant
> to support a wide range of protocols, not just HTTP commands, and
> presumably the design suits that. But the way it depends so heavily
> on the interrelated classes and yet the class API docs lack any
> documentation of these relationships, is quite frustrating.
>
> Steven J. Owens
> [EMAIL PROTECTED]
> [EMAIL PROTECTED]
>
>
___________________________________________________________________________
> To unsubscribe, send email to [EMAIL PROTECTED] and include in the
body
> of the message "signoff SERVLET-INTEREST".
>
> Archives: http://archives.java.sun.com/archives/servlet-interest.html
> Resources: http://java.sun.com/products/servlet/external-resources.html
> LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
>
___________________________________________________________________________
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff SERVLET-INTEREST".
Archives: http://archives.java.sun.com/archives/servlet-interest.html
Resources: http://java.sun.com/products/servlet/external-resources.html
LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
