Forum Discussion

Hoang_Hung's avatar
Hoang_Hung
Icon for Cirrus rankCirrus
Jul 14, 2022
Solved

Monitor Layer 7

Dear all I have a backend use web service port 8010. After I have using monitoring layer 7 but it not working. I have tried curl-v https://abc:8010/swagger/index.html Response:  > GET /swagger/in...
application delivery
  • StephanManthey's avatar
    StephanManthey
    Jul 15, 2022

    Please try a Send-string of (and make sure to replace the hostname of abc with the hostname you were actually using in your cURL request):

    GET /swagger/index.html HTTP/1.1\r\nHost: abc:8010\r\nUser-Agent: curl/7.79.1\r\nAccept: */*\r\n\r\n

    ... and a Receive-string of (accepting status codes of 200 or 301 or 301). This string is handled as a non case-sensitive regular expression:

    ^HTTP/1\.[01]\s+(200|301|302)

     It will look for a response using HTTP/1.0 or HTTP/1.1 followed by at least one whitespace character (\s+) followed by one of the acceptable status code.

    If you are absolutely sure there will be a HTTP/1.1 200 OK in the response, you can put it in as well. The dot (.) in "HTTP/1.1" is handled as a wildcard (it is still treated as a regexp), but this shouldn´t matter.

    Keep in mind, that some webservers don´t reply with a reason phrase (here it is the OK; might be MOVED PERMANENTLY, FOUND etc.). That´s why it is now best practice not to include it in your receive string. 

StephanManthey's avatar
StephanManthey
Icon for MVP rankMVP
Jul 14, 2022

As Dario_Garrido wrote, adding the http protocol and the host header does the trick.

Without adding the protocol your server will very likely respond with a bad request (status code 400), because it assumes you are trying to use HTTP/0.9.

Please see this article for details: https://developer.mozilla.org/en-US/docs/Web/HTTP/Basics_of_HTTP/Evolution_of_HTTP 

Even the BIG-IP automatically adds a double carriage return / line feed sequence by default, it is best practice to add it yourself in the send-string:

GET /<filename/path> HTTP/1.1\r\nHost: <hostname>\r\n\r\n
    • StephanManthey's avatar
      StephanManthey
      Icon for MVP rankMVP
      Jul 15, 2022

      Please try a Send-string of (and make sure to replace the hostname of abc with the hostname you were actually using in your cURL request):

      GET /swagger/index.html HTTP/1.1\r\nHost: abc:8010\r\nUser-Agent: curl/7.79.1\r\nAccept: */*\r\n\r\n

      ... and a Receive-string of (accepting status codes of 200 or 301 or 301). This string is handled as a non case-sensitive regular expression:

      ^HTTP/1\.[01]\s+(200|301|302)

       It will look for a response using HTTP/1.0 or HTTP/1.1 followed by at least one whitespace character (\s+) followed by one of the acceptable status code.

      If you are absolutely sure there will be a HTTP/1.1 200 OK in the response, you can put it in as well. The dot (.) in "HTTP/1.1" is handled as a wildcard (it is still treated as a regexp), but this shouldn´t matter.

      Keep in mind, that some webservers don´t reply with a reason phrase (here it is the OK; might be MOVED PERMANENTLY, FOUND etc.). That´s why it is now best practice not to include it in your receive string.