Forum Discussion
HTTP SOAP XML monitor help needed
- Apr 08, 2021
Ok this is solved now. Looks like monitor does not like or does not know how to deal with compression. I should have paid more attention to Accept-Encoding header that was included in my send string as my intent was to mimic the request from SOAP UI. That's why all those hexidecimals where showing in the monitor log. My send string was instructing server side to send compressed response that monitor failed to decompress. That simple!. Once, [Accept-Encoding: gzip,deflate] was removed, the response was now sent in plain text and I was able to see in the monitor log.
For a troubleshooting purpose, enable monitor logging option for one of the member. Logs would be created in /var/log/monitors/ directory. It would show request and response. Compare it with the curl output and try to adjust the send/receive string accordingly. Please note, logging should be disabled after troubleshooting.
You can also post the curl ouput and monitor logs here and someone can take a look.
That response that I have posted above is what I see in the monitor log. My send string seems to be ok as I can see request from the monitor on the xml gateway. What is confusing is why I am seeing the receive string in hex. That is the part I don't get.
- spalandeApr 07, 2021Nacreous
Can you post curl output also here to see if you get the correct response?
Recent Discussions
Related Content
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com