Because it allows us to have multiple machines serving one URL without
having multiple SSL certificates. It also offloads SSL encryption to
dedicated hardware. Those are the main reasons.
Stefán F. Stefánsson wrote:
>
> Any particular reason you're using a proxy instead of Tomcats built in
> HTTPS support? (it came with 3.2 so you need to get that version if
> you're not already using it).
>
> Regards, Stefan.
>
> -----Original Message-----
> From: Geoff Lane [mailto:[EMAIL PROTECTED]]
> Sent: 29. janúar 2001 23:31
> To: [EMAIL PROTECTED]
> Subject: HTTPS to HTTP proxying
>
> Ok, so
> I have a situation where we are doing an HTTPS to HTTP proxy.
> Essentially a proxy recieves the HTTPS request, makes an HTTP request to
> the server with Tomcat running standalone and then the response is
> returned through the proxy back to the user.
>
> So, I access something like: https://somehost/index.html and there is a
> redirect in it like: out.sendRedirect( "nextpage.html" );
> Tomcat in this case will return the user to
> http://somehost/nextpage.html (notice no https). This makes some sense
> because Tomcat sees the scheme as HTTP not HTTPS. The odd part though is
> that this same setup worked with Java Web Server.
>
> Anyone know how to handle this other than rewriting all of the redirects
> to absolute URLs?
> Thanks.
>
> --
> Geoff Lane <[EMAIL PROTECTED]>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, email: [EMAIL PROTECTED]
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, email: [EMAIL PROTECTED]
--
-------------------------------------------
Geoff Lane <[EMAIL PROTECTED]>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
