Forum Discussion

Alen_Ismic_1869's avatar
Alen_Ismic_1869
Icon for Nimbostratus rankNimbostratus
Apr 02, 2015

LocalTraffic::Policies

Version of BIG IP: 11.4.0 HF7

 

When I try to create classic redirect policies Target: http-reply Event: request Action: redirect parameters: location https://[getfield [HTTP::host] ":" 1][HTTP::uri]

 

I get this one: Major application error.

 

When I do same on another BIG IP, version 11.4.1 I create policies successfuly. I made like this: https://support.f5.com/kb/en-us/solutions/public/14000/900/sol14996.html

 

On one system work, on another no, both are physical appliances.

 

application delivery
deployment
LTM

4 Replies

Sort By
  • Hannes_Rapp's avatar
    Hannes_Rapp
    Icon for Nimbostratus rankNimbostratus
    Apr 02, 2015

    Would it stop complaining on 11.4.0 if you replaced the code with?

     

    https://[getfield [HTTP::host] {:} 1][HTTP::uri]

    Also, you could implement a simpler code to handle your HTTPS redirects.

     

    https://[HTTP::host][HTTP::uri]

    The only difference is that the first code would not include the port specification with the redirect. For example, "http://www.mysite.com:8080/page1" would be redirected to "https://www.mysite.com/page1" when using the first code sample, but would be redirected to "https://www.mysite.com:8080/page1" when using the second sample. You have to use the 1st code if a non-standard port specification is made inside the HTTP Host header. In all other cases, the second code will do.

     

  • Hannes_Rapp_162's avatar
    Hannes_Rapp_162
    Icon for Nacreous rankNacreous
    Apr 02, 2015

    Would it stop complaining on 11.4.0 if you replaced the code with?

     

    https://[getfield [HTTP::host] {:} 1][HTTP::uri]

    Also, you could implement a simpler code to handle your HTTPS redirects.

     

    https://[HTTP::host][HTTP::uri]

    The only difference is that the first code would not include the port specification with the redirect. For example, "http://www.mysite.com:8080/page1" would be redirected to "https://www.mysite.com/page1" when using the first code sample, but would be redirected to "https://www.mysite.com:8080/page1" when using the second sample. You have to use the 1st code if a non-standard port specification is made inside the HTTP Host header. In all other cases, the second code will do.