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
Oh, I figured it out! I was wrong; this is not a bug, it's just that the Wiki page is wrong! The correct way to use "noserver" is to put it after the content, not before. So:
when HTTP_REQUEST {
HTTP::respond 200 content {
blahblahblah
} noserver
}
should work just fine. I'll update the Wiki....
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
