Forum Discussion
Slow response via VS than direct - why?
Hello F5 folks,
I have a very simple Virtual Server configuration with clientssl and http profiles and source_addr persistence.
Users of the thick-client are complaining that responses are slower via VS than via direct connection to the back-end servers (load-balanced by the VS).
Snooping on the server-side (ie. cleartext between F5 and back-end server), I've only noticed two unusual traffic characteristics:
-
server response contains "Content-Type: text/html" header but the actual entity-payload is binary (I'd say 'application/octet-stream' is more appropriate); and
-
the client's requests contain "Expect: 100-continue" header and await "HTTP/1.1 100 Continue" response before sending entity-payload.
Can either of these cause slow-down that I'm experiencing?
R's, Alex
2 Replies
- Max_Q_factor
Cirrocumulus
You might want to check the following links:
Devcentral: Expect: 100-continue header and Big-IP 100 responses
SOL15164: HTTP POST requests to a BIG-IP APM virtual server may be delayed
- epaalx
Cirrus
Hi Max, thanks for response. I ended up substituting "tcp-lan-optimized" for "tcp" profile and the latency went away. R's, Alex
Help guide the future of your DevCentral Community!
What tools do you use to collaborate? (1min - anonymous)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