Forum Discussion
HTTP send string limit
Hi,
I am attempting to monitor OCSP responders using an actual OCSP request via a custom monitor using HTTP as the parent monitor.
In a few other posts I've seen external monitor solutions that use "openssl ocsp ..." as a solution. This will certainly work. But, our LTM is heavily used and I'm concernced about resource utilization on the device. External monitors aren't nearly as efficient.
An HTTP health monitor will only look at the first 5120 bytes of an HTTP response. I need to discover what this limit is on the send string.
An HTTP send string appears to only support 100 bytes. I determined this by doing a tcpdump on the monitor and only seeing 100 bytes of a 185 byte string that was entered. (full packets were captured)
Is there a 100 byte limit on the size of the send-string, or is there some other problem? If so, can it be expanded? Has anyone else tried to do what we're trying to do?
We are using version 11.6.
I'm new to DevCentral and hope I haven't missed this answer somewhere else.
Thanks!
2 Replies
- Brian-2_246870
Nimbostratus
An update... It appears to stop after the first 20 bytes of content. HTTP headers of varying length does not seem to impact what is sent. What is puzzling is that if all the content is printable ascii, it will send all the content. But if any of it is binary, then it only takes the first 20 bytes.
- Brian-2_246870
Nimbostratus
We have found the problem. Binary data is being sent as part of the content. The 21st byte is a null byte. I've found posts from 7 years ago that say a null char is not permitted in a send string. Apparently, that is still the case.
Help guide the future of your DevCentral Community!
What tools do you use to collaborate? (1min - anonymous)Recent Discussions
Related Content
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com