Forum Discussion
NimbostratusEditing JSON HTTP Response
EmployeeIs http:// and :80 in the payload or headers?
For example, you'd normally see this in Location headers (redirects) and in payload data referencing document objects. But if in payload, it's probably better to avoid regex and just do multiple string maps.
when HTTP_RESPONSE_DATA {
set payload [string map [list "\}\}\}\}" "\}\}"] [HTTP::payload]]
set payload [string map [list "http://" "https://"] [HTTP::payload]]
set payload [string map [list ":80" ""] [HTTP::payload]]
HTTP::payload replace 0 $clen $payload $fixeddata1
HTTP::release
}What you're doing is grabbing the existing payload into a variable, making changes to that variable, and then completely replacing the HTTP::payload with the contents of that variable.
NimbostratusJust to confirm that this works for you to replace the brackets?
We've just implemented this change and it still doesn't want to replace them...
- Kevin_Stewart
Try this:
when HTTP_RESPONSE_DATA { log local0. "payload before: [HTTP::payload]" set payload [string map [list "\}\}\}\}" "\}\}"] [HTTP::payload]] set payload [string map [list "http://" "https://"] [HTTP::payload]] set payload [string map [list ":80" ""] [HTTP::payload]] log local0. "payload after: $payload" HTTP::payload replace 0 $clen $payload $fixeddata1 HTTP::release }Tail the LTM log:
tail -f /var/log/ltmAnd send a request. This should show you the payload before and after manipulation.
- Chris_Bates
Okay... so this was interesting...
After checking the logs both the before and after payloads did not have the 4 brackets. So somewhere else these are being added...
- Kevin_Stewart
Might there be another iRule and/or device in front of this handling HTTP? Or maybe some client side JavaScript that could be modifying the response?
