Forum Discussion
Russell_E_Glaue
Nimbostratus
Feb 18, 2009The noserver option of HTTP::respond sends back an invalid HTTP format or Content-length
When I use the following code:
HTTP::respond 200 content {
...
}
I get the following back in a web client HTTP request:
...
spark_86682
Feb 19, 2009Historic F5 Account
EDIT: This isn't true; see my next post
I must disagree with cmbhatt; this looks like a bug to me. I would definitely open a case with F5 support on this issue. In the meantime, you should probably use "TCP::respond" as a workaround.
Recent Discussions
Related Content
DevCentral Quicklinks
* 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
Discover DevCentral Connects
