Forum Discussion

Robert_77728's avatar
Robert_77728
Icon for Nimbostratus rankNimbostratus
Nov 20, 2013

HTTP 404 through Big-IP but NO 404 error going directly to the server?

What would cause a HTTP 404 error going through Big-IP LTM v10.2.2 but if you go directly to the server via IP address you can view the page? In the past, users that usually get this are either blocked by their firewall or proxy server but this user sits right next to me within the "green zone" of our network.

 

The URL through Big-IP is http://www.test.com/test/ and the direct URL is http://10.194.4.99/test/

 

Any ideas?

 

BIG-IP Access Policy Manager (APM)
design
management
security

5 Replies

  • Thomas_Gobet's avatar
    Thomas_Gobet
    Icon for Nimbostratus rankNimbostratus
    Nov 20, 2013

    Did you check your virtual hosts on your webservers ?

     

    If you add an entry in your host file to reach your webserver with the fqdn and not an IP, does it work ?

     

  • Robert_77728's avatar
    Robert_77728
    Icon for Nimbostratus rankNimbostratus
    Nov 20, 2013

    Thanks. Should it look like this...

    10.194.4.99     www.test.com    MyServerNameHere
  • cdougall_14195's avatar
    cdougall_14195
    Icon for Cirrus rankCirrus
    Nov 20, 2013

    Yes, that what he means. 10.194.4.99 www.test.com MyServerNameHere

     

    Using the host file in that way, you simulating everything from the failing call other than going through the load balance. Basically having the same HTTP headers hit the node when calling directly as you do when going through the VIP.

     

    This will help you isolate the issue to the server or to the VIP configuration.

     

  • Kevin_Stewart's avatar
    Kevin_Stewart
    Icon for Employee rankEmployee
    Nov 20, 2013

    If I may add, if your Hosts file entry wasn't correct, and you weren't pointing directly to the VIP, then you wouldn't be getting a 404 response. This error indicates that you're asking for something that the server thinks does not exist.

     

    The bad news is, there can be a myriad of reasons why an application server might generate this message, aside from an actual "file not found". The best way forward, I believe, is to:

     

    1. First validate that requests are actually making it to the web server through the F5. This is a simple tcpdump to watch traffic on the internal getting to the server. If that's good, then

       

    2. Inspect the client side of the HTTP dialog. Look at what the client is asking for and what the server is sending. You may find that the server is sending references to page objects using an internal URL.

       

    3. Finally, look at the web server logs. You should see the requested object and the 404 status.

       

  • mfkk531_168091's avatar
    mfkk531_168091
    Icon for Nimbostratus rankNimbostratus
    Jul 13, 2015

    Hi Everyone, Im having the exact same issue.

     

    Can you please confirm what the resolution action was for this issue?

     

    Did adding that help to host files

     

    10.194.4.99 www.test.com MyServerNameHere

     

    Many Thanks