Forum Discussion
NimbostratusForward URI to different pool on a Virtual server using SSL
I am able to successfully forward a uri starting with /abc to a specific pool on virtual server using SSL. I have implemented this using a policy based on this https://support.f5.com/kb/en-us/solutions/public/15000/000/sol15097.html. The problem I have is that if I enter the uri directly from the web browser https://domain.com/abc -- it fails I believe due to SSL, this working fine on a virtual server using only port 80. However, if I first enter https://domain.com first and then specify the path https://domain.com/abc it works? Anyone know whats going on. Thanks.
10 Replies
Yann_DesmarestCirrus
Hello,
What happen if you capture the traffic using fiddler for example ? Can you give more details on your configuration ?
Mali47_261353Okay, I have virtual server that is terminating client-ssl within this same virtual server I have an ltm policy applied that forwards a URI starting with /abc to another pool. When I type the full path using https://domain.com/abc the connection is reset -- I captured using wireshark and inspect element via chrome - this is basically my configuration. If I remove SSL from the virtual server everything works fine. When I type the full path using https://domain.com/abc the connection is reset. However, If I do access the main website first using https://domain.com and then subsequently enter https://domain.com/abc it works fine. Thanks.
Yann_Desmarest_Nacreous
Hello,
What happen if you capture the traffic using fiddler for example ? Can you give more details on your configuration ?
- Mali47_261353Okay, I have virtual server that is terminating client-ssl within this same virtual server I have an ltm policy applied that forwards a URI starting with /abc to another pool. When I type the full path using https://domain.com/abc the connection is reset -- I captured using wireshark and inspect element via chrome - this is basically my configuration. If I remove SSL from the virtual server everything works fine. When I type the full path using https://domain.com/abc the connection is reset. However, If I do access the main website first using https://domain.com and then subsequently enter https://domain.com/abc it works fine. Thanks.
- Yann_Desmarest
It's like the VS is not able to bind your connection to a pool
You can troubleshoot the tcp reset by enabling tcp reset logging :
https://support.f5.com/kb/en-us/solutions/public/13000/200/sol13223.html?sr=53370751
Then, you will see tcp reset reason within the ltm log file
- Mali47_261353I dont see any resets from the log, i had reset feature enabled from before, as I said when using http and no ssl I have no problems
- Mali47_261353If possible you can try simulating this, creating a virtual server with ssl and apply a policy forwarding a specific path to a pool and try what I did.
- Yann_Desmarest_
It's like the VS is not able to bind your connection to a pool
You can troubleshoot the tcp reset by enabling tcp reset logging :
https://support.f5.com/kb/en-us/solutions/public/13000/200/sol13223.html?sr=53370751
Then, you will see tcp reset reason within the ltm log file
- Mali47_261353I dont see any resets from the log, i had reset feature enabled from before, as I said when using http and no ssl I have no problems
- Mali47_261353If possible you can try simulating this, creating a virtual server with ssl and apply a policy forwarding a specific path to a pool and try what I did.
