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

Eddie_27920's avatar
Eddie_27920
Icon for Nimbostratus rankNimbostratus
Jul 20, 2015

I am having trouble getting a custom GET / health monitor set up. Trying 1st in CLI.

Hi, I am following all the examples I have seen here so far and cannot get the CLI to return anything but "Write error: Connection reset by peer". Here is my command: echo -e "GET / HTTP/1.1\r\nhost: url/Reports/Pages/Folder.aspx Close\r\n" | nc IP address 443 I am looking to the specific page, if it responds with anything except the 200 OK then mark the node down. I thought I would test the GET 1st but like I said I get write error every time. I need the monitor to go all the way to this specific page. Can anyone see what my issue might be? Other than lack of experience :)

 

Thanks, Eddie

 

5 Replies

  • I have also tried with the same results of the write error connection closed as mentioned above. echo -e "GET /Reports/Pages/Folder.aspx HTTP/1.1\r\nhost: url\r\nConnection: Close\r\n\r\n" | nc IP address 443
  • Okay, well that at least indicates that you can get past the SSL. Now it's saying that the requested resource isn't available. Are you certain of this URI?

     

  • We are thinking we may need to authenticate according to the server app owner

     

    What kind of authentication?

     

  • I believe the issue is that netcat isn't going to do the SSL negotiation. You could use openssl s_client, but it'd probably be easier to use cURL: curl -k https://192.168.5.198:443/Reports/Pages/Folder.aspx -H "Connection: close"

     

  • No. You're doing the cURL in place of the netcat. Not combined.

    curl -k https://sqlreports.dev.mesaaz.gov/Reports/Pages/Folder.aspx -H "Connection: Close"
    

    If you get a 404 response, that almost always means that the resource you're asking for doesn't exist, not that there's an authentication error. An auth error is usually a 401, though it is conceivably possible for an application to throw a 404 if auth fails (not typical though).