Forum Discussion

Nimbostratus

Oct 17, 2022

Editing JSON HTTP Response

Hey guys! I'm completely new to F5 and am currently trying to fix an issue that we are having with 'HTTP' to 'HTTPS' rewrites. There was another post that fixed somewhat the issue that we are faci...

application delivery

devops

Chris_Bates

Nimbostratus

Oct 19, 2022

Just 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

Employee

Oct 19, 2022

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/ltm

And send a request. This should show you the payload before and after manipulation.

Chris_Bates
Nimbostratus
Oct 20, 2022
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
Employee
Oct 20, 2022
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?
Chris_Bates
Nimbostratus
Oct 21, 2022
Yeah, that's what I'm thinking...
I've asked the networking team to take a look. Thanks for the help 🙂
Leslie_Hubertus
Ret. Employee
Oct 25, 2022
Now I'm curious - did they figure out the issue, Chris_Bates?
Chris_Bates
Nimbostratus
Oct 31, 2022
Not as of yet. The networking team are adamant that there are no other rules that could affect this despite the logs showing that it's the most likely cause.
We are arranging a meeting this week with F5 to get to the bottom of it hopefully...