Forum Discussion

opers13_3280's avatar
opers13_3280
Icon for Nimbostratus rankNimbostratus
Feb 06, 2011

Issue with http and https VS

I'm having issues getting the following to work, two Virtual servers with the same IP 10.10.10.1:HTTP and HTTPS

 

Single HTTP pool configured. HTTP redirects to HTTPS VS assigned to the HTTP VS.

 

 

The goal is to have the HTTP VS with an irule redirecting HTTP to HTTPS VS and no pool assigned to HTTP VS.

 

When I configure the HTTP VS like that, nothing works..including the HTTPS VS.

 

 

But when I remove the irule and assign the HTTP pool to the HTTP VS both HTTP and HTTPS VS work just fine...not sure exactly what's going on.

 

 

virtual exchange-443 {

 

enable

 

translate address enable

 

translate service enable

 

snatpool none

 

pool exchange

 

destination 10.10.10.1:https

 

mask 255.255.255.255

 

profiles

 

exch-oneconnect

 

exch-owa-443

 

exch-owa-tcp-443

 

serverside

 

exchange_owa_SSL

 

clientside

 

tcp

 

clientside

 

persist exch-owa-cookie-443

 

 

 

}

 

virtual exchange-80 {

 

enable

 

translate address enable

 

translate service enable

 

pool

 

snat none

 

pool exchange

 

fallback persist none

 

destination 10.10.10.1:http

 

mask 255.255.255.255

 

profiles

 

exch-owa-80

 

exch-owa-tcp-80

 

oneconnect

 

persist exch-owa-cookie-80

 

 

pool exchange {

 

lb method round robin

 

snat enable

 

nat enable

 

slow ramp time 0

 

monitor all http

 

members

 

10.20.20.10:http

 

up

 

10.20.20.11:http

 

up

 

 

rule exch_owa_http to https {

 

when HTTP_REQUEST {

 

HTTP::redirect "https://10.10.10.1/owa[HTTP::uri]"

 

}

 

 

Thanks

 

 

  • Can you create a custom HTTP profile and configure the 'header to insert' as "FRONT-END-HTTPS: on", add that profile to the HTTPS virtual server, add the redirect iRule to the HTTP virtual server, remove the pool from the HTTP virtual server and retest? If you run into any issues, try using a browser plugin like HttpFox for Firefox or Fiddler2 to see what's happening from the client perspective.

     

     

    Aaron
  • Hi aaron,

     

     

    I think I found the issue..it was the irule.

     

     

    I installed HttpFox and noticed the extra /owa in the redirect.

     

     

    https://10.10.10.1/owa/owa

     

     

    I removed the /owa from the irule redirect URL and now it seems to be working fine.