Forum Discussion

Raghbir_Singh_S's avatar
Raghbir_Singh_S
Icon for Nimbostratus rankNimbostratus
Jun 21, 2011
Solved

Replace HTTPS://xxxx.xxxx.com with HTTP://xxxx.xxxx.com

Our F5 is terminating SSL traffic and sending HTTP request on port 80 to back-end server. However I also would like to change the HTTP request from "HTTPS://xxxx.xxx.com" to "HTTP://xxx.xxx.com" and send it to the back-end server. The back-end server is causing problem with request coming as "HTTPS://xxxx.xxxx.com"

 

 

I would like have the iRule in-place in F5 to solve above problem.

 

 

 

Please help.

 

 

 

Thanks,

 

RSS

 

application delivery
dev
devops
iRules
  • Colin_Walker_12's avatar
    Colin_Walker_12
    Jun 21, 2011
    All you would need to do is a header replace, assuming you don't want to send a redirect back to the client. The command you're looking for is HTTP::header replace

     

     

    Click Here

     

     

    Keep in mind that you might need to deal with the content being sent back to the client as well, though, to avoid your users being redirected to the new URI by the server, depending on the response. Just something to look out for.

     

     

    Colin

4 Replies

Sort By
  • nitass's avatar
    nitass
    Icon for Employee rankEmployee
    Jun 21, 2011
    if u are using only clientssl profile, i understand bigip is already sends request in form of http://xxx.xxx.com to server.
  • hooleylist's avatar
    hooleylist
    Icon for Cirrostratus rankCirrostratus
    Jun 21, 2011
    Hi RSS,

     

     

    Can you post an anonymized copy of a request you'd like to modify? Is the https:// reference in the requested URI? Or somewhere else like the request payload? You can use a browser plugin like HttpFox for Firefox or Fiddler2 to record the request headers.

     

     

    Aaron
  • Colin_Walker_12's avatar
    Colin_Walker_12
    Historic F5 Account
    Jun 21, 2011
    All you would need to do is a header replace, assuming you don't want to send a redirect back to the client. The command you're looking for is HTTP::header replace

     

     

    Click Here

     

     

    Keep in mind that you might need to deal with the content being sent back to the client as well, though, to avoid your users being redirected to the new URI by the server, depending on the response. Just something to look out for.

     

     

    Colin