Forum Discussion
Torti
Cirrus
Cirrusno response if the code is invalid @ v.11.0.2
Hi,
the editor seems to have a problem to process the response from the bigip @ >v11.2.0, if there is an error inside the irule.
I didn't test it with v11.0.0.
The only message is at the bottom of the irule editor: The response isn't a well-formed xml-code (I got a message in german)
This is the message in the LTM log: Rule [/Common/iRuler_Parse_Test_Rule] error: line 1: [parse error: missing close-brace] [{ set uri [HTTP::uri] set remote_addr [IP::remote_addr] set query [HTTP::query] if { $query eq "wsdl" } { log local0. "URL contains query $query" }] line 2: [command is not valid in the current scope] [set uri [HTTP::uri]] line 2: [command is not valid in the current scope] [HTTP::uri] line 3: [command is not valid in the current scope] [set remote_addr [IP::remote_addr]] line 3: [command is not valid in the current scope] [IP::remote_addr] line 4: [command is not valid in the current scope] [set query [HTTP::query]] line 4: [command is not valid in the current scope] [HTTP::query] line 6: [command is not valid in the current scope] [if { $query eq "wsdl" } { log local0. "URL contains query $query" }]
I did test it with LTM+ASM@v11.2.0 & LTM+ASM@v11.3.0
2 Replies
Tortiomg, the message is really hard to read. Can someone fix the problems with the forum?- Ultimately this means you have an error in your iRule and so it cannot be saved.
The error message you're seeing isn't terribly helpful though. On the java side this actually turns out to be (largely) an Ajax issue. I assume it's the same on the .net side but I'm not sure what library is being used for iRuler. The response back in XML includes the entirety of that log message which you posted. Some character in there isn't valid for XML 1.0 so the XML library throws an error. For java there's no flag in Ajax to tell it to accept non-compliant XML so depending on your error message you may get the non-well formatted XML error reported back to you instead of the actual iRule error message. I don't think there's anything that can be done aside from patching Ajax itself.
