Forum Discussion
Sep 07, 2012
Hi Michael
Thanks for your answer. We're transferring encrypted uid's. The size of the responses are between 0,5kb and 8 kb.
Compression is turned on and caching is not necessary since each request is more or less unique.
I tried OneConnect too, but it did not make any difference.
Here's what we've done so far:
1. Wan-optimized and lan-optimized tcp profiles. Slow.
2. Regular TCP profiles on both client and server side. OK speed.
3. Performance HTTP. Very fast.
What I can't figure out though is how the https can be terminated with the Performance HTTP server since there's no option to specify an HTTPS profile. I even changed browsers in between to rule out caching but they all show the correct certificate.
I'd be happy to use the Performance HTTP type, but only if I can figure out exactly how the SSL termination works.
Any ideas?