CSS Bypassing farm traffic based on matching HTTP header

Answered Question
Sep 9th, 2008

Hi,

I am trying to find out whether the CSS is able to bypass specific traffic.

I have an existing content to match all HTTP and send to a farm. However, there are some HTTP flows i dont want to goto the farm, i just want CSS to route them onward to the destination. These specific HTTP packets are differentiated by the host field in the header. What config is needed to allow these host annotated packets to bypass the serverfarm?

Thanks

Alan

I have this problem too.
0 votes
Correct Answer by Gilles Dufour about 8 years 2 months ago

Alan,

when you configure a url "//..../" the css will look for the ... inside the hostname header field. Not the url itself.

so my config is correct :-)

G.

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (1 ratings)
Loading.
Gilles Dufour Tue, 09/16/2008 - 01:08

Alan,

create a service with the default gateway (or next-hop) ip address.

Make the service 'type transparent'

Duplicate your current content rule that catches the traffic and add the command url "//

I believe this should work.

Gilles.

alanwright1 Tue, 09/16/2008 - 03:22

Hi Gilles,

Thanks for your response. The only thing you may have misread is that i need to select the host header field, as the URL's may not have host part in them, ie. raw http, not proxied. I guess then i need a header match rule linked to the new content, instead of the URL filter you mentioned.

BR

Alan

Correct Answer
Gilles Dufour Tue, 09/16/2008 - 05:05

Alan,

when you configure a url "//..../" the css will look for the ... inside the hostname header field. Not the url itself.

so my config is correct :-)

G.

Actions

This Discussion