Forum Discussion

dmshunevich_262's avatar
dmshunevich_262
Icon for Nimbostratus rankNimbostratus
Oct 15, 2016

HTTP on 8080 port

Hello I have VS running on 8080 port. Service running on 8080 servers port. When I trying access to server directly http://abc.com:8080 its work fine. But when I start using F5, I can't open this link. Could someone please explain how I can resolve this issue?

 

Here iRules which I use when HTTP_REQUEST { switch [string tolower [HTTP::host]] { abc.com { pool abc_8080_POOL } } }

 

7 Replies

  • nathe's avatar
    nathe
    Icon for Cirrocumulus rankCirrocumulus

    The DCers may need more info on this. How is your virtual setup? What does "can't open the link" actually mean? Please provide more info to help.

     

  • Is the VS listening on port 80 or 8080 ?

     

    Are the pool members configured to listen on port 8080 ?

     

    Any SSL termination ?

     

  • VS listening port 8080. Pool members listening 8080. NO SSL. Issue was with adding port in http host header field (http://abc.com:8080) I resolved this issue using following i rule:

      when HTTP_REQUEST {  
    
      Replace host header value with everything before the colon  
     HTTP::header replace Host "[getfield [HTTP::host] : 1]"  
    

    }

    and then choose appropriate pool based on http host header without pool. Could you please advise that this is correct way ?

    • Vijay_E's avatar
      Vijay_E
      Icon for Cirrus rankCirrus

      Can you not set up VS to listen on port 80 and leave the pool members to listen on port 8080 ? This will remove the need for the iRule.

       

    • Ryannnnnnnnn's avatar
      Ryannnnnnnnn
      Icon for Altocumulus rankAltocumulus

      agreed (ensure to enable port translation in the VS settings).

       

  • Thanks for yours responses. But I can't change vs to 80 port since port 8080 is hard coded in application.

     

    • Vijay_E's avatar
      Vijay_E
      Icon for Cirrus rankCirrus

      8080 can be hardcoded and the server will be receiving the traffic on 8080.

       

      Client > VS:80 > Server:8080

       

      I am not sure if you have taken that into consideration.