Re: FrontEnd/BackEnd Vs ISA (reverse proxy)

From: Jim Harrison [MSFT] (jmharr_at_online.microsoft.com)
Date: 03/31/04 

Date: Wed, 31 Mar 2004 09:20:39 -0800

I hate to disappoint you, but there is no enforced relationship between HTTPS and GZIP compression.
Exch FE/BE communications are DCOM. 

-- 
 Jim Harrison [ISASE]
 Read the help, books and articles!
 This posting is provided "AS IS" with no warranties, and confers no rights.
"FE" <frederic@esnouf.net> wrote in message news:u12wBjvFEHA.696@TK2MSFTNGP12.phx.gbl...
Hi,
Thanks to all for these info.
First, I checked the whitepaper about ISA and Exchange 2003. It explains how
to implement it, but ... it assumes (figure1) that the FE and the BE are on
the same LAN which is not what I will have to do.
My research are not between the Client/ISA/FE ... It is more between the FE
and the BE servers.
Since the BE are Windows 2003, and because I will have a poor bandwidth
between FE and BE, I must use HTTPS to be able to use compression (GZIP) and
web page authentication.
So my question is :
    * How the BE and the FE discuss ? HTTP or HTTPS ? Can I force HTTPS
between them ?
If I cannot force HTTPS for FE/BE communication, I will not be able to use
GZIP... which is bad.
I you can advise me ...
Thanks to all again.
FE
"FE" <frederic@esnouf.net> wrote in message
news:OUxngdjFEHA.3252@TK2MSFTNGP11.phx.gbl...
> Hi,
>
> I need to implement Exchange 2003 on several sites (1 org). I have one
main
> site (with the internet connection) and a few remote site with a very a
poor
> connection (1 E2003 per site, and 1 local DC/GC).
>
> The customer want OWA ... for all the users (from the internet not for
> internal use)
>
> I have in DMZ an ISA Server used for reverse proxy.
>
> I must use HTTPS so I will be able to use GZIP (and the web page for
> authentication)... and so compress the data transfered from the remote
sites
> (poor link) to the remote user (connected somewhere on the internet).
>
>
> I have 2 options :
>     1) use ISA as a revers proxy, and use 1 URL per remote server
> (site1.owa.company.com, poorsite1.owa.company.com, ...)
>     2) install a FrontEnd on the main site.
>
> Question 1 : If I use a frontend server, how will be the dialog between
the
> FE and the remote BE server (with a URL such as
> https://poorsite1.owa.company.com/exchange) ? HTTPS or HTTP ? If I check
the
> documentation about Exchange 2000 (even if I use E2003), they say that the
> dialog is HTTP between the FE and the BE. If the dialog is HTTP I cannot
use
> GZIP which is not good.
>
> Question 2 : what is the best in a performance point of view ? User a
> FrontEnd or user ISA as a revers proxy ?
>
> Thanks for your advices.
>
> Regards
>
> FE
>
>

Relevant Pages

  • ModSSL - Knoppix 3.3
    ... I create some server key & crt. ... i can do http request but NOT https request with a remote client ...
    (Focus-Linux)
  • Re: ModSSL - Knoppix 3.3
    ... > I create some server key & crt. ... I think you're mixing the virtual hosts too. ... > from REMOTE: ssh ok, http ok, https NOK. ...
    (Focus-Linux)
  • Re: FrontEnd/BackEnd Vs ISA (reverse proxy)
    ... but there is no enforced relationship between HTTPS and GZIP compression. ... > I have in DMZ an ISA Server used for reverse proxy. ... and so compress the data transfered from the remote ...
    (microsoft.public.exchange.connectivity)
  • Re: FrontEnd/BackEnd Vs ISA (reverse proxy)
    ... but there is no enforced relationship between HTTPS and GZIP compression. ... > I have in DMZ an ISA Server used for reverse proxy. ... and so compress the data transfered from the remote ...
    (microsoft.public.isaserver)
  • Re: FrontEnd/BackEnd Vs ISA (reverse proxy)
    ... but there is no enforced relationship between HTTPS and GZIP compression. ... > I have in DMZ an ISA Server used for reverse proxy. ... and so compress the data transfered from the remote ...
    (microsoft.public.exchange2000.protocols)