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

cxcal_18687's avatar
cxcal_18687
Icon for Nimbostratus rankNimbostratus
Jan 22, 2009

Unruly Health Monitor

This been a thorn in my side for weeks now...     Trying to get a HTTP monitor to do a simple "GET /ms/alive.txt HTTP/1.1 \nHOST:\n" with a Receive Value of "Alive!"     The lin...
management
monitoring
hoolio's avatar
hoolio
Icon for Cirrostratus rankCirrostratus
Jan 27, 2009
RFC2616 states:

HTTP/1.1 defines the sequence CR LF as the end-of-line marker for all

protocol elements except the entity-body (see appendix 19.3 for

tolerant applications).

I didn't know about any automatic translation of \n to CRLF in previous versions. 9.4.6 doesn't seem to do this: 

 
  b monitor http_1.1_test_monitor list 
 monitor http_1.1_test_monitor { 
    defaults from http 
    recv "200 OK" 
    send "GET / HTTP/1.1\nHost: \nConnection: Close" 
 }

tcpdump shows the \n (0a) are not translated to \r\n (0d0a):

0x0030 18d5 dcf9 e6d2 22c6 4745 5420 2f20 4854 ......".GET./.HT

0x0040 5450 2f31 2e31 0a48 6f73 743a 200a 436f TP/1.1.Host:..Co

0x0050 6e6e 6563 7469 6f6e 3a20 436c 6f73 650d nnection:.Close.

0x0060 0a0d 0a ...

Annoyingly enough, two CRLF's are automatically appended to the send string regardless of whether it's legal for the specific HTTP request or not.

Aaron