Sorry Server for CSS 11500

[net-harry]

Hi,

I have a question regarding sorry server configuration on the CSS 11500 series.

Is there a way for the sorry server to ignore the URL path and always send the user traffic to the "root" page (e.g. index.html) of the sorry server web server?

The problem I have is the redirection of the "root" page (url "/") that is configured for the normal traffic is causing the sorry page not to work since the URL path ("/psp/CUSTOMER1/?cmd=login") does not exist on the sorry page web server:

service Sorry-Server
  protocol tcp
  port 8000
  keepalive type tcp
  ip address 192.168.2.254
  active

service server1
  ip address 192.168.2.101
  protocol tcp
  keepalive type tcp
  port 8080
  active

service server2
  ip address 192.168.2.102
  protocol tcp
  keepalive type tcp
  port 8080
  active

owner Customer1
  content Content1
    vip address 192.168.1.101
    port 80
    protocol tcp
    url "/*"
    balance aca
    advanced-balance arrowpoint-cookie
    flow-timeout-multiplier 6
    add service server1
    add service server2
    primarySorryServer Sorry-Server
    active

  content Content1-Redirect
    redirect "/psp/CUSTOMER1/?cmd=login"
    vip address 192.168.1.101
    port 80
    protocol tcp
    url "/"
    active

Thanks in advance for your help!

Best regards,

Harry

[Gilles Dufour · Accepted solution]

Create a redirect service and use it in place of your current sorryserver.

This way, you redirect the user to http://192.168.2.254:8000/ and the request will go directly to the sorry server on the right url.

Gilles.

[net-harry]

Dear Gilles,

Thank you very much for your answer!

Could you please confirm if the following would be sufficiant and the correct configuration for the service if I have not modified the default prepend-http option:

service Sorry-Server
  type redirect
  redirect-string "192.168.2.254:8000"

Thanks again for your help!

Best regards,

Harry

[net-harry]

Hi again,

During a maintenance window I made the following change and that made things a bit better:

service Sorry-Server
  type redirect
  keepalive type none
  redirect-string "192.168.2.254:8000"
  active

However, since the redirect string points to a private address, Internet users are not able to access the URL.

As a work-around I sent the redirect to a new content rule with a public address and then configured a second sorry page server:

service Sorry-Server
  type redirect
  keepalive type none
  redirect-string "sorry.example.com:8000"
  active

service Sorry-Server-2
  ip address 192.168.2.254
  protocol tcp
  port 8000
  keepalive type tcp
  active

owner Customer1
  content Content2
    vip address x.x.x.x

    add service Sorry-Server-2
    port 8000
    protocol tcp
    active

Is there a better way to do this?

Best regards,

Harry