the stream prematurely or not at all.
If I attempt to call the server using CURL it works fine.
Thanks,
Eben Calhoun
// attachmentId is just an integer.
Reference referenceforUpload = new
Reference("http://localhost:8080/restApp/attachment/"; + attachmentId);
FileInputStream fis =
Hi!
Ok, so I just tried using HttpClient directly with the
EasySSLProtocolSocketFactory. HttpClient was able to communicate fine with
my Restlet server via HTTPS with my self-signed certificate.
On Thu, Jun 19, 2008 at 7:38 PM, Eben <[EMAIL PROTECTED]> wrote:
> Hello,
>
> I w
s?
This would be a nice feature to have for doing testing. Or when the program
doesn't really care about the origins of a certificate of the other party,
just that it uses a secure channel to communicate.
-Eben
PM, Thierry Boileau <[EMAIL PROTECTED]>
wrote:
> Hello Eben,
>
> My first quick answer: if you want to authenticate a request, you should
> use the ChallengeResponse object (see
> http://www.restlet.org/documentation/1.1/tutorial#part09).
ava:80)
at
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684)
at java.lang.Thread.run(Thread.java:595)
I have other Restlet client code that works fine, although the calls are not
authenticated in those instances.
Thanks!
-Eben Calhoun
Hello Thierry,
Tests passed. Servlet connector working perfectly with 1.1m2 release.
Thank you for releasing this!
-Eben
On Fri, Feb 29, 2008 at 2:44 AM, Thierry Boileau <[EMAIL PROTECTED]>
wrote:
> Hello Eben,
>
> here is a new snapshot:
> http://www.restlet.org/down
d
the same problem using a Tomcat 6 version.
I tried having the Restlet get connected using both the Component and
Application classes.
-Eben
7 matches
Mail list logo
