Forum Discussion
hoolio
Cirrostratus
Nov 21, 2007Valid events in STREAM_MATCHED event? (avoiding
Hi,
I was thinking that you could make decisions based on request or response data without actually collecting the HTTP data by using the stream profile. For example, this person (Click her...
spark_86682
Nov 27, 2007Historic F5 Account
Unfortunately, this really can't be done. Since the stream profile is designed to do minimal buffering of server response data, it's quite possible that the client would already have gotten part of the server response by the time the STREAM_MATCHED event fired. So if you could successfully do an HTTP::retry in that event, then the client could see part of the first response followed by all of the second, which is almost certainly not what you want. That's why it's critical to actually buffer the server response if you might retry the request (so the client only ever sees one response).
As far as a workaround, well, if you know that the error string always appears in the first N bytes, you could use TCP level commands to only buffer that many bytes, which would at least minimize the amount of buffering you do.
Help guide the future of your DevCentral Community!
What tools do you use to collaborate? (1min - anonymous)Recent Discussions
Related Content
DevCentral Quicklinks
* 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
Discover DevCentral Connects