For more information regarding the security incident at F5, the actions we are taking to address it, and our ongoing efforts to protect our customers, click here.

Forum Discussion

Sean_Lagerholm_'s avatar
Sean_Lagerholm_
Icon for Nimbostratus rankNimbostratus
Jun 07, 2006

Simple http redirect???

Help, I'm having difficulty with fulfilling a requirement :

 

 

The customer wants to type in some url and then gets redirected.

 

The customer doesn't want to see the redirect in their browser.

 

 

It should work like this :

 

 

in the browser type : http://somesite.com

 

 

The request gets proxied by the BigIP to http://anothersite.com/stuff

 

 

(the client never sees the http://anothersite.com/stuff in their browser.

 

 

Is this a redirect or a rewrite???

 

 

Thanks!!!

 

 

12 Replies

  • Deb_Allen_18's avatar
    Deb_Allen_18
    Historic F5 Account
    To define a class:

     

     

    I keep forgetting they are called "Data Group Lists" now, which might have made that easier to figure out -- sorry!

     

     

    In the GUI, go to the iRules window & you'll see a "Data Group Lists" tab. Click there to Create a new class of type String, and enter a row for each virtual server with a space between each field.

     

     

    /deb

     

  • unRuleY_95363's avatar
    unRuleY_95363
    Historic F5 Account
    Ok, you're on the right track now deb! I was mainly referring to the lack of the HTTP_RESPONSE_DATA event, but I'm glad you read up on the chunking too.

     

     

    As for the syntax checking allowing HTTP::payload in HTTP_RESPONSE - Well, generally speaking, the syntax checker only applies validation regarding the namespace of commands and the events they are found in. For example, the HTTP:: commands must be in HTTP_ events. Of course, there are lots of exceptions and these are usually added as they are discovered and fine tuned. We have also often ended up being too restrictive and then had to relax the validation. So, I'd be reluctant add that restriction.

     

     

    Plus, I'm not sure whether there might be a case when HTTP::payload would be used in HTTP_RESPONSE (bl0ndie might be able to clarify that).

     

     

    It will also be nice someday when the GUI will support warnings and we could warn about any questionable presence of a command. Until then...