Hello,

OK, I've done it : the SSL authentication of my tomcat server works pretty
fine. I'm currently using port 8443, though. But this is not my question.

The real question is a bit more weird. If I try & connect to my server on
port 8443, but with just http protocol (no encryption), Tomcat responds by
sending a file ! It is a .bin file which name is :

- either the context name of my request (for instance, if I ask
http://myserver.com/qwerty the file is called qwerty.bin)
- either a random (?) name if I ask the context name of my webapp.

Do you have an idea why & how to get rid of this, anyone ?

Cheers,

Pierre



2007/7/31, Pierre Goupil <[EMAIL PROTECTED]>:
>
> Ooops... Yes, definitely... But I still need the port 80 for my purely
> static (unencrypted) content. The connections to my webapp will be encrypted
> from end-to-end using its context name, but all the content accessible
> within the default context will be static.
>
>
> Pierre
>
>
>
> 2007/7/31, David Smith <[EMAIL PROTECTED]>:
> >
> > Port 80 is for unencrypted traffic.  The default port for SSL (https
> > protocol) is 443.
> >
> > --David
> >
> > Pierre Goupil wrote:
> >
> > >I have some static HTML content. But I will handle it with Tomcat too,
> > in
> > >order to ease things regarding my present need.
> > >
> > >So I will stick to Tomcat for SSL management and won't use Apache
> > *Httpd*
> > >;-) any more... Easy. As easy as my need in fact. Actually, my only
> > >"sensitive" need is to have SSL connections from end-to-end, as this is
> > an
> > >application for a persons & goods security firm. I don't want to take
> > any
> > >risk with this kind of data.
> > >
> > >I'm going to investigate the use of port 80 with tomcat, now !
> > >
> > >Thanx again !
> > >
> > >Pierre
> > >
> > >
> > >
> > >2007/7/31, Caldarale, Charles R < [EMAIL PROTECTED]>:
> > >
> > >
> > >>>From: Pierre Goupil [mailto:[EMAIL PROTECTED]
> > >>>Subject: Re: secured authentication / connection
> > >>>
> > >>>But I still need Apache in front of it, in order
> > >>>to be able to use the port 80 & this sort of things.
> > >>>
> > >>>
> > >>Tomcat can quite happily use port 80; what else do you need httpd for?
> >
> > >>
> > >>(We'll assume you mean httpd when you refer to Apache, since both
> > Tomcat
> > >>and httpd are Apache products.)
> > >>
> > >>- Chuck
> > >>
> > >>
> > >>THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE
> > PROPRIETARY
> > >>MATERIAL and is thus for use only by the intended recipient. If you
> > >>received this in error, please contact the sender and delete the
> > e-mail
> > >>and its attachments from all computers.
> > >>
> > >>---------------------------------------------------------------------
> > >>To start a new topic, e-mail: users@tomcat.apache.org
> > >>To unsubscribe, e-mail: [EMAIL PROTECTED]
> > >>For additional commands, e-mail: [EMAIL PROTECTED]
> > >>
> > >>
> > >>
> > >>
> > >
> > >
> > >
> > >
> >
> >
> > ---------------------------------------------------------------------
> > To start a new topic, e-mail: users@tomcat.apache.org
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
>
>
> --
> "Si le sang ne coule pas assez chaud dans tes veines,
> je le répandrais sur le sable pour qu'il bouille au soleil."
>
> (Maraxus de Kelde)
>



-- 
"Si le sang ne coule pas assez chaud dans tes veines,
je le répandrais sur le sable pour qu'il bouille au soleil."

(Maraxus de Kelde)

Reply via email to