# Health monitor with login check and content length

**URL:** <https://community.f5.com/t/health-monitor-with-login-check-and-content-length/51011>\
**Category:** Technical Forums\
**Tags:** ltm, application-delivery\
**Created:** [June 25, 2019, 3:03pm UTC](https://community.f5.com/t/health-monitor-with-login-check-and-content-length/51011 "2019-06-25T15:03:39Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![David\_M\_1](https://avatars.discourse-cdn.com/v4/letter/d/76d3ee/32.png) [@David\_M\_1](https://community.f5.com/u/David_M_1)\
**Post date:** [June 25, 2019, 3:03pm UTC](https://community.f5.com/t/health-monitor-with-login-check-and-content-length/51011/1 "2019-06-25T15:03:39Z")

</div>

I found SOL : [myF5](https://support.f5.com/csp/article/K1033?sr=58157087)

It says:

To create an HTTP 1.1 post, use the following syntax:

POST /MyApp.cgi HTTP/1.1\r\nHost: [host.domain.com](http://host.domain.com)\r\nConnection: Close\r\nContent-Length: 10\r\nAuthorization: Basic \<string\>\r\n\r\0123456789

In this syntax, note the following: \<string\> is the output from step 1

For example:

```tcl
POST /MyApp.cgi HTTP/1.1\r\nHost: host.domain.com\r\nConnection: Close\r\nContent-Length: 10\r\nAuthorization: Basic ZjU6ZjVwYXNzd2Q=\r\n\r\0123456789

```

In these examples, your content length of 10 would match the length of your message body, which in this example is 0123456789.

You do not need to specify a user name and password in the monitor configuration when performing this workaround.

----------------

What exactly is the last message body part? Why is it required and what value do we need to use there?

Is it just some placeholder to simulate a real request?

---

<div class="post-metadata">

**Author:** ![Dario\_Garrido](https://avatars.discourse-cdn.com/v4/letter/d/d2c977/32.png) [@Dario\_Garrido](https://community.f5.com/u/Dario_Garrido)\
**Post date:** [June 25, 2019, 6:18pm UTC](https://community.f5.com/t/health-monitor-with-login-check-and-content-length/51011/2 "2019-06-25T18:18:15Z")

</div>

Hello David.

It’s just an example, POST request usually includes a payload message which could be required by the server. As far as I know, POST wo/payload is perfectly RFC compliant, so it depends of your backend server.

[https://stackoverflow.com/questions/4191593/is-it-considered-bad-practice-to-perform-http-post-without-entity-body](https://stackoverflow.com/questions/4191593/is-it-considered-bad-practice-to-perform-http-post-without-entity-body)

BTW, there is a mistake in the example:

“…Authorization: Basic ZjU6ZjVwYXNzd2Q=_ **\r\n\r\n** _0123456789”

KR,

Dario.

---

<div class="post-metadata">

**Author:** ![David\_M\_1](https://avatars.discourse-cdn.com/v4/letter/d/76d3ee/32.png) [@David\_M\_1](https://community.f5.com/u/David_M_1)\
**Post date:** [July 2, 2019, 7:23am UTC](https://community.f5.com/t/health-monitor-with-login-check-and-content-length/51011/3 "2019-07-02T07:23:49Z")

</div>

Alright, thanks!
