Forum Discussion

Russell_E_Glaue's avatar
Russell_E_Glaue
Icon for Nimbostratus rankNimbostratus
Feb 18, 2009

The 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:   ...
application delivery
dev
devops
iRules
spark_86682's avatar
spark_86682
Historic F5 Account
Feb 18, 2009
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....