Forum Discussion
M, thanks for your reply, and also happy to see we're not the only one in the world using the Forward Proxy iApp! And would you believe I just got this resolved a few weeks ago? I did not need to change the resolver address but that is good information to know how to do that.
Here's something that may help if you move to v16. The HTTP:discard disable command, used by the Forward Proxy iApp in HTTP CONNECT methods, is not operating as it should on v16 and is currently in the bug tracker under Bug ID# 1284589, which may be again be updated in the future to 1284589-2 as a bug on top of a bug was also found in our troubleshooting with F5 Support.
https://cdn.f5.com/product/bugtracker/ID1284589.html
F5 Engineering provided us with a hotfix that resolves the issue completely as replacing "HTTP:disable discard" with "HTTP:disable" does not fully fix the issue. If using the FP iApp and v16 an EHF needs to requested from F5 referencing that bug ID, until when/if the fix makes it into a firmware release.
Appreciate your response and hope that helps in the future!