Thierry, Thierry Boileau <thboileau <at> gmail.com> writes: > I'm not able to reproduce all your problems. Well you got some similar ones.
> I switch the "type" parameter in order to use NIO (1) or BIO > (2). Am I wrong? Thats what I did (but I wished that it wasn't called "type"). > > When using BIO : > - if I provide wrong passwords, the server crashes when > starting. Yes. > - if I provide right passwords, Jetty send a weird file > with odd characters for every request. I only get this if my client connects with the http scheme. https seems to work. But this behaviour is very strange! Is it jetty? > > When using NIO : > - if I provide wrong passwords, the server loops when starting, > because of NullPointerExceptions that seem to be badly managed. Absolutely. > - if I provide right passwords, the server hangs, but I don't > know if it is the consequence of my request, of if the server > is stille starting. Yes. I also suspect that its still starting, mainly because the BIO connector logs a few more debug messages during startup. What I was trying to do is this: write an insecure app that will redirect to a secure one. I'm trying to do this using a single component, filtering http and https connections to different virtual hosts. Does this seem reasonable? I'm going to experiment with these recent versions of jetty6.1 a bit. Nick
