Does anyone know of any problem that would be created by
having HTTPS listen at port 80, with HTTP disabled?
Ed.
Milt Epstein wrote:
> On Mon, 29 Nov 1999, YekSoon Lok wrote:
>
> > Hi,
> >
> > I'm using JWS2.0.
> >
> > Currently, I have an application running at say
> > http://domainname (using the port 80)
> >
> > I enabled the secure webservice (HTTPS).
> >
> > How can I have it that users can continue accessing the site
> > typing either
> > 1. http://domainname
> > 2. https://domainname
> >
> > Do I need to do some mapping somewhere and which port should
> > each listener be listening to. (HTTP and HTTPS)
>
> You cannot have HTTP and HTTPS running on the same port. They are two
> distinct communication protocols, and they each need to be running on
> their own port (if you want to run both, that is -- there is nothing
> stopping you from running just one or the other). The reason neither
> of the above URLs (one with "http" and one with "https") don't need a
> port specified is that each of the protocols has a default port -- for
> HTTP it is 80 and for HTTPS it is 443. It is only if you vary from
> these default ports (for either HTTP or HTTPS) that you need to
> specify a port in the URL.
>
> I don't know the details of configuring HTTP and HTTPS servers for
> JWS, so you will have to check the documentation for that.
___________________________________________________________________________
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
