Forum Discussion
Russell_Moore_8
Jun 01, 2012Nimbostratus
Aaron,
That's the ID I was sent too. I was provided a sample code that could be a work around but we are determining if we want to use it or wait for a patch to fix the leak.
This is the sample and reasoning I was given:
A base64 query string length should be always divisible by 4. So,
when HTTP_REQUEST {
catch {
if { ![expr [string length [HTTP::query]]%4] } {
b64decode [HTTP::query]
} else {
puts "Bad 64base input."
}
}
}
I'm not sure about the logic here as it would seem to read "if the query string length is NOT divisible by 4 then base64 decode". This seems to be reverse of what would be needed.